Power Your Software Testing with AI Agents and Cloud
The Native AI-Agentic Cloud Platform to Supercharge Quality Engineering. Test Intelligently and Ship Faster.
- TestMu AI (Formerly LambdaTest)
- /
- Blog
- /
- Automate Mobile CI/CD Testing: TestMu AI and Appcircle Integration
Automate Mobile CI/CD Testing: TestMu AI and Appcircle Integration
Run Espresso tests on real Android devices from your Appcircle pipeline with the TestMu AI integration: setup, variables and results, with no device lab.
Last Updated on:
Mobile teams can build an app in minutes, but a fast pipeline only helps if the build is tested on the devices your users actually own. Keeping testing in a separate, manual step slows every release down.
TestMu AI now integrates with Appcircle, so your Appcircle workflow can run automated Espresso tests on real Android devices in the TestMu AI cloud, with no device lab to maintain. The setup reference lives in Appcircle's guide to the TestMu AI and Appcircle Espresso step.
TL;DR
- The TestMu AI and Appcircle integration runs Espresso tests on real Android devices straight from an Appcircle workflow.
- Appcircle still lists the step as LambdaTest App Automate - Espresso, since TestMu AI was formerly called LambdaTest.
- The Android Build for UI Testing step must run first to produce the app APK and the test APK.
- The step needs a TestMu AI username and access key, stored in an Appcircle environment variable group.
- Test results are written to $AC_LT_TEST_RESULT_PATH so later workflow steps can report on them.
What Is Appcircle?
Appcircle is an enterprise mobile CI/CD platform that automates building, testing, signing and distributing iOS and Android apps. It runs on the public cloud, private cloud (GCP, AWS, Azure), hybrid setups and on-premises, so it suits organizations with strict hosting requirements. If you are still comparing pipelines, see our roundup of the best CI/CD tools.
Key highlights include:
- Faster releases: Automated workflows cut app release time from days to minutes.
- Flexible integration: Hundreds of workflow steps, plus tools such as Fastlane and SonarQube.
- Unified code signing: Signing certificates and profiles are managed in one place across apps and environments.
- Enterprise-ready: Built-in security, SSO and compliance controls for regulated industries.
Why Does Mobile CI/CD Need Testing Built In?
Speed alone is not enough in mobile delivery. Without automated mobile app testing inside the pipeline, fast releases can ship bugs, performance problems or crashes on devices nobody tried.
- Device fragmentation: Android runs on a huge range of screen sizes, hardware and OS versions. Testing on real devices in the pipeline catches device-specific issues before release.
- Faster feedback: Tests that run on every build flag a bug in the same cycle that introduced it, which keeps it cheap to fix.
- No device lab: Buying and maintaining physical devices drains engineering time. A cloud device farm removes that cost and covers far more devices than most teams could keep in-house.
- Room to scale: As the app and the team grow, Android automation testing on the cloud grows with the pipeline, without adding devices or people to run them.
Note: Run your Appcircle builds on real Android devices in the cloud. Sign up for TestMu AI today!
How Does the TestMu AI Integration With Appcircle Work?
The integration uses TestMu AI App Automation, which runs automated Espresso tests for Android apps on the TestMu AI real device cloud. Once the step is in your workflow, every build uploads the APKs, runs the tests and returns the results without anyone starting a test run by hand.
Setting Up the TestMu AI Integration in Appcircle
Step 1: Add the prerequisite build step
Add the Android Build for UI Testing step to your Appcircle workflow before the TestMu AI step. It builds both the application APK and the Espresso test APK, which the TestMu AI step needs.
Then add the TestMu AI step itself. In Appcircle it is still listed under its former name, LambdaTest App Automate - Espresso.
Step 2: Configure environment variables
Store your TestMu AI credentials as environment variables in your Appcircle project. Both are required to authenticate API requests:
- Username ($AC_LT_USERNAME): Your TestMu AI account username.
- Access key ($AC_LT_ACCESS_KEY): Your TestMu AI account access key.
Security note: Keep usernames and access keys in an Appcircle environment variable group instead of hardcoding them in the workflow.
Step 3: Configure input variables
The step reads these inputs:
- APK path ($AC_LT_APK_PATH): Path to the application APK, filled in automatically by the Android Build for UI Testing step.
- Test APK path ($AC_LT_TEST_APK_PATH): Path to the Espresso test APK, also filled in by that build step.
- Test configuration ($AC_LT_PAYLOAD): Optional JSON string with your test configuration. The app and test APK URLs are inserted into it automatically.
- Timeout ($AC_LT_TIMEOUT): Test execution timeout in seconds. The default is 600.
Step 4: Run and review the results
On each run, the step uploads both APKs to TestMu AI, executes your Espresso tests on real Android devices, and writes the results to $AC_LT_TEST_RESULT_PATH. That path defaults to a directory under $AC_OUTPUT_DIR, so later steps in the workflow can pick up the results for reporting.
The step is open source. You can read it in the Appcircle TestMu AI Espresso App Automate component repository.
Running the tests is only half the upkeep; someone still has to write and maintain the Espresso suite as the app changes. If your team would rather describe mobile flows in plain English, KaneAI, the TestMu AI testing agent, can author Android app tests from natural-language instructions and update them when the UI shifts, running on the same real device cloud.
All in All
The Appcircle and TestMu AI integration puts real-device testing inside the mobile pipeline, so every Android build is checked on real hardware before it ships, without a device lab to run.
To start, add the Android Build for UI Testing step and the LambdaTest App Automate - Espresso step to one workflow, set your two credentials, and run a build. The TestMu AI app testing guide covers how app tests run on the device cloud. The integration is available on free and paid plans; share feedback in the TestMu AI Community, over chat, or at support@testmuai.com.
Happy Testing!
Author
Reviewer
Shivam Singh
Reviewer
Shivam Singh is a Lead Member of Technical Staff at TestMu AI (formerly LambdaTest), architecting the Real Device Cloud that runs automated app and web tests on real Android and iOS devices. He designed the architecture for real-device app and web automation and wrote the microservices from scratch in Golang, including the XCUITest and Espresso execution layers for iOS and Android. His platform reached peak parallel concurrency of 150+ for app automation while handling roughly 500,000 tests a month, and he leads the team that keeps the automation grid running. He brings over eight years of engineering experience and holds a B.Tech in Computer Science.
TestMu AI and Appcircle Integration FAQs
Did you find this page helpful?
More Related Blogs
TestMu AI forEnterprise
Get access to solutions built on Enterprise
grade security, privacy, & compliance
- Advanced access controls
- Advanced data retention rules
- Advanced Local Testing
- Premium Support options
- Early access to beta features
- Private Slack Channel
- Unlimited Manual Accessibility DevTools Tests