Developer Tools

Automating Mobile App Testing with AWS Device Farm - Real Device Testing and CI/CD Integration

Run automated tests on real iOS and Android devices and integrate them into your CI/CD pipeline. This article covers test framework selection criteria and manual testing via remote access.

約 3 分で読めます

Overview of Device Farm

Device Farm is a service that lets you test mobile and web applications on real devices hosted by AWS. Over 2,500 device configurations are available, including Samsung Galaxy, Google Pixel, iPhone, and iPad, covering multiple OS generations. The service offers two modes: automated testing (running test scripts) and remote access (manually operating a real device). Pricing is pay-per-minute per device, and a monthly flat-rate unlimited plan is also available.

Test Frameworks and Automated Testing

Device Farm supports Appium (Java, Python, Node.js, Ruby), Espresso (Android), XCTest/XCUITest (iOS), and Calabash. For cross-platform testing, Appium is the best choice because you can test both iOS and Android with the same test code. The built-in test suite runs basic tests without writing any test code. Fuzz testing generates random user actions to detect crashes, and Explorer testing automatically navigates through app screens and captures screenshots. Test results include logs, screenshots, videos, and performance data (CPU, memory, network), which help reproduce issues and identify root causes.

CI/CD Pipeline Integration

By adding a Device Farm action to the test stage of CodePipeline, you can automatically run device tests after each build. When a test fails, the pipeline stops, preventing buggy builds from being deployed to production. You can also create Device Farm test runs from Jenkins or GitHub Actions via the AWS CLI or SDK. Device pools define which devices to test on, covering key device and OS version combinations. Testing on every device is time-consuming and costly, so a practical strategy is to prioritize devices with the highest market share and vary the number of target devices between full pre-release tests and daily smoke tests. If you want to learn more about Device Farm in depth, related books (Amazon) can be a helpful resource.

Device Farm Pricing

Device Farm offers two pricing models. Pay-per-use charges approximately $0.17 per minute per device. The flat-rate plan costs $250 per month for unlimited use of a single device, with multi-device flat-rate plans also available. If you run tests daily through a CI/CD pipeline, the flat-rate plan becomes more cost-effective once your monthly test time exceeds about 25 hours. Remote access (manual testing) costs approximately $0.17 per minute. The first 1,000 device minutes are included in the free trial.

Summary

Device Farm is a service that automates mobile app testing on real devices. You can run automated tests with major test frameworks across hundreds of devices without purchasing or managing them. By integrating Device Farm into your CI/CD pipeline, you can detect device-specific bugs early and release high-quality mobile applications.

Related Services

AWS Device FarmA cloud testing service that lets you test applications on real mobile devices and browsersAWS CodePipelineA service for building and automating CI/CD pipelines from source to deployment

Related Articles

AWS CodeDeploy Deployment Strategies - Blue/Green Deployments for EC2, ECS, and LambdaManage deployment strategies across three platforms - EC2, ECS, and Lambda - in a unified way. This article covers ECS blue/green deployments and automatic rollback triggered by CloudWatch alarms.Streamlining Team Development with Kiro - Unifying Quality Through Steering Files and Spec SharingShare design intent across your team with spec-driven development and unify coding conventions with steering files. This article explains how to automate checks with Agent Hooks and streamline the review process.Mobile App Test Automation - Building a Real Device Testing Platform with AWS Device FarmLearn how to automate mobile application testing on real devices with AWS Device Farm, integrate tests into CI/CD pipelines with Amplify, and ensure quality across diverse devices.

More on This Topic

How AI-DLC Transforms Software Development - A Practical Guide to the Inception, Construction, and Operation PhasesAn overview of the AI-DLC methodology that places AI at the center of the development process. Learn about the three phases of Inception, Construction, and Operation, and how to put them into practice with Kiro and Amazon Q Developer.Hands-On with the AI-DLC Unicorn Gym Workshop - Learning AI-DLC Through Team DevelopmentA complete look at the hands-on workshop where you experience AI-DLC through three days of team development. Learn how to run Mob Elaboration and Mob Construction, and how to leverage open-source workflows.Visually Design Serverless Applications with AWS Application Composer - Automatic IaC Template GenerationLearn about visual design of serverless architectures with Application Composer, automatic SAM template generation, and VS Code integration.Artifact Repository Management - Building a Secure Package Management Platform with AWS CodeArtifactLearn how to build and operate an artifact repository using AWS CodeArtifact. This guide covers centralizing package management for npm, Maven, PyPI, and more, along with building secure build pipelines through CodeBuild integration.How AWS API Throttling Works - The Token Bucket Algorithm and the Truth Behind 429 ErrorsLearn how AWS API rate limiting is implemented using the token bucket algorithm, understand the concept of burst capacity, explore differences in throttling limits across services, and discover practical strategies to avoid throttling.Why AWS APIs Return XML - The Evolution from Query APIs to REST JSONExplore the historical reasons why S3 and EC2 APIs return XML responses, the differences between Query APIs and REST APIs, the evolution of authentication from Signature V2 to V4, and the complexity that SDKs abstract away.Why AWS API Endpoints Differ by Region - The Design of Global and Regional ServicesWe explain the design reasons behind the separation of regional endpoints like ec2.us-east-1.amazonaws.com and global endpoints like iam.amazonaws.com, as well as the existence of dual-stack and FIPS endpoints.Browser-Based Shell Environment - Instant CLI Access with AWS CloudShellExplains the browser-based shell environment powered by AWS CloudShell. Covers the CLI environment available instantly from the AWS Management Console, pre-installed development tools, automatic IAM authentication integration, secure file management, and practical tips for improving operational efficiency.

Similar Articles and Services

Mobile App Test Automation - Building a Real Device Testing Platform with AWS Device FarmLearn how to automate mobile application testing on real devices with AWS Device Farm, integrate tests into CI/CD pipelines with Amplify, and ensure quality across diverse devices.AWS Device FarmA cloud testing service for running application tests on real mobile devices and browsersIoT Device Management - Building a Scalable IoT Platform with AWS IoT Core and LambdaLearn how to build an IoT device management platform using AWS IoT Core and Lambda.IoT Device Connectivity with AWS IoT Core - MQTT Communication and Device ShadowsConnect IoT devices via MQTT, synchronize state with device shadows, route data with the rules engine, and design device authentication for secure IoT solutions.