Skip to content

docs(espresso): migrate EspressoTestingSidebar docs and sidebar #3645

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
keys-github wants to merge 8 commits into
base: stage
Choose a base branch
from
Open

docs(espresso): migrate EspressoTestingSidebar docs and sidebar #3645

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
8 commits
Select commit Hold shift + click to select a range
71c7f84
docs(espresso): migrate EspressoTestingSidebar docs, sidebar, and dev…
salmanlt Oct 3, 2026
af3407e
Merge branch 'stage' into espresso-testing-migration
keys-github Oct 6, 2026
f6cb6d7
docs(espresso): add "End-to-End (E2E) testing" keyword to intro
salmanlt Oct 18, 2026
45b788c
docs: align Article schema headline with page title
salmanlt Oct 18, 2026
a4d5846
Synced Espresso docs
salmanlt Oct 25, 2026
63bf367
Merge remote-tracking branch 'upstream/stage' into espresso-testing-m…
salmanlt Oct 26, 2026
0e9fa5e
Fix stage merge: drop duplicated Espresso intro, restore sidebar exports
salmanlt Oct 26, 2026
5acbc97
Merge remote-tracking branch 'upstream/stage' into espresso-testing-m…
salmanlt Oct 31, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
90 changes: 72 additions & 18 deletions docs/debugging-espresso-tests.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,12 +1,16 @@
---
id: debug-espresso-tests
title: How to debug your Espresso tests
title: How to Debug and Troubleshoot Espresso Tests on TestMu AI
hide_title: true
toc_max_heading_level: 2
sidebar_label: Debug Espresso Tests
description: Learn how to debug Espresso tests for your mobile applications to resolve different kinds of bugs for your failed test builds.
description: Debug and troubleshoot Espresso tests on TestMu AI using instrumentation, network logs, video recordings, and a reference of build and shard errors.
keywords:
- debug espresso tests
- how to debug espresso tests
- troubleshoot espresso tests
- espresso build errors
- espresso shard errors
- mobile app testing
url: https://www.testmuai.com/support/docs/debugging-espresso-tests/
site_name: TestMu AI
Expand All @@ -33,7 +37,7 @@ import VerifiedTag from '@site/src/component/verifiedTag';
},{
"@type": "ListItem",
"position": 3,
"name": "Debugging your Espresso Tests",
"name": "How to Debug Espresso Tests on TestMu AI",
"item": `${BRAND_URL}/support/docs/debugging-espresso-tests/`
}]
})
Expand All @@ -51,7 +55,7 @@ import VerifiedTag from '@site/src/component/verifiedTag';
"@type": "WebPage",
"@id": "https://www.testmuai.com/support/docs/debugging-espresso-tests/"
},
"headline": "How to debug your Espresso tests",
"headline": "How to Debug and Troubleshoot Espresso Tests on TestMu AI",
"description": "Learn how to debug Espresso tests for your mobile applications to resolve different kinds of bugs for your failed test builds.",
"url": "https://www.testmuai.com/support/docs/debugging-espresso-tests/",
"image": {
Expand Down Expand Up @@ -114,21 +118,21 @@ import VerifiedTag from '@site/src/component/verifiedTag';
}) }}
/>

# Debugging Your Espresso Tests
***
# How to Debug and Troubleshoot Espresso Tests on TestMu AI
---

Learn how to debug Espresso tests for your mobile applications to resolve different kinds of bugs for your failed tests/builds.
Debugging Espresso tests on <BrandName /> uses instrumentation, device, and network logs plus video recordings to pinpoint the root cause of failed tests and builds. A reference of common build and shard errors with explanations helps you diagnose issues fast.

## Objective
***
---

By the end of this guide, you will be able to:

* Resolve different kinds of bugs due to which your test/build failed.
* Understand the reasoning behind the same.

## Debugging Tests
***
---

<BrandName /> offers a variety of logs to help you locate the root cause:

Expand Down Expand Up @@ -161,7 +165,6 @@ curl -u "YOUR_LAMBDATEST_USERNAME:YOUR_LAMBDATEST_ACCESSKEY" \
Replace `<YOUR_BUILD_ID>` with your actual build ID.
#### Sharded Builds
For sharded builds, use the following curl command:

<VerifiedTag value="Verified" />

```bash
Expand Down Expand Up @@ -209,11 +212,66 @@ KEY|VALUE|DESCRIPTION
--|--|--
| video | TYPE: BOOLEAN <br/> DEFAULT: TRUE <br/> `video= TRUE`<br/> OR `video = FALSE` | Video recording of the complete screen |

Refer to our [Espresso testing documentation](/support/docs/getting-started-with-espresso-testing/#capabilities-supported) for more capabilities.
Refer to our [Espresso testing documentation](/support/docs/espresso-supported-capabilities/) for more capabilities.

>
If you still have any questions for us, please feel free to let us know via our <span className="doc__lt" onClick={() => window.openLTChatWidget()}>**24X7 Chat Portal**</span> or mail us to support@testmuai.com
## Troubleshooting Espresso Tests
---

Beyond the logs above, the tables below list the common errors encountered when running Espresso tests on <BrandName />. Understanding these errors and their explanations can help you diagnose and resolve issues during your test execution on <BrandName />.

### Espresso Build Errors

This table highlights the errors encountered when running tests on [<BrandName /> Real Devices without shards](/support/docs/getting-started-with-espresso-testing/).

<img loading="lazy" src={require('../assets/images/debug-espresso-test/5.png').default} alt="Image" width="1347" Height="610" className="doc_img"/> <br />

<!-- Verified 2026-09-11: each fix restates the root cause given in this table. -->

| Build Execution Errors | Root Cause of Error | How to Fix |
|--------------------------------------------|--------------------------|----------|
|Application under test provided by you did not get installed. Please check the application.| The target application failed to install on the selected device during test execution. This indicates an issue with the provided application file or incompatibility with the chosen device configuration.| Check the application file, and that it is compatible with the device you chose, then upload it again. |
|Test Suite provided by you did not get installed. Please check the application.| This indicates that the test suite you provided could not be installed on the chosen <BrandName /> environment. This might be due to invalid test suite files, incompatibility issues, or missing dependencies.| Check the test suite file for problems, compatibility issues, and missing dependencies, then upload it again. |
|Failed to fetch runner class for test extraction. Please recheck your test suite.| Test discovery failed. The system couldn't extract test cases or classes from the provided test suite application. This might be due to issues with the test suite app itself or its configuration.| Check the test suite app and its configuration, then upload it again. |
|Failed to extract classes or tests from runner app - test discovery failed.| Test discovery failed. The system couldn't extract test cases or classes from the provided runner application. This might be due to issues with the test suite app itself or an incompatibility with the testing framework used. | Check the test suite app and that it works with your testing framework, then upload it again. |
|No tests found in the test suite. Please check your test suite or applied filters.| The test execution framework couldn't locate any test cases to run due to: <br /> <b>Empty Test Suite: </b>Ensure your test suite contains at least one test class with a @Test annotated method.<br /> <b>Incorrect Filtering: </b>Verify that any applied test filters aren't accidentally excluding all tests. You can see more on espresso test filtering [here](/support/docs/speedup-espresso/).| Add at least one `@Test` method, and check that your filters do not exclude every test. |
|Tests could not be run as localization setup failed. Please check locale and try again.| The test suite encountered a localization setup error. This means the system's locale or language settings could not be configured correctly. Please verify your locale settings and try re-running the tests. | Check your locale settings, then run the tests again. |
|Oops! An error occurred at our end. Please try again.| A temporary infrastructure issue arose. While a device was allocated for your test, it became unavailable before the test execution started. Please retry the test or reach out to support@testmuai.com if the issue persists. | Run the test again. If it keeps happening, contact support@testmuai.com. |
|Desired Capabilities Error. Please check the desired capabilities that you have passed.| The test encountered a [`Desired Capabilities`](/support/docs/espresso-supported-capabilities/) Error. This indicates an issue with the configuration provided for the test execution. Please verify the values you have set for desired capabilities like device, platform, or application path. | Check the device, platform, and application path values against the [supported capabilities](/support/docs/espresso-supported-capabilities/). |

### Espresso via HyperExecute Shard Errors

This table highlights the errors encountered when running espresso tests with [Shards via HyperExecute](/support/docs/sharding-espresso-rd-hyperexecute/) on <BrandName /> Real Device Cloud.

<img loading="lazy" src={require('../assets/images/debug-espresso-test/4.png').default} alt="Image" width="1347" Height="610" className="doc_img"/> <br />

<!-- Verified 2026-09-11: each fix restates the root cause given in this table. -->

| Shard Execution Errors | Root Cause of Error | How to Fix |
|--------------------------------------------|--------------------------|----------|
|Application under test provided by you did not get installed. Please check the application.| The target application failed to install on the selected device during test execution. This indicates an issue with the provided application file (APK/IPA) or incompatibility with the chosen device configuration.| Check the application file, and that it is compatible with the device you chose, then upload it again. |
|Test Suite provided by you did not get installed. Please check the application.| This indicates that the test suite you provided could not be installed on the chosen <BrandName /> environment. This might be due to invalid test suite files, incompatibility issues, or missing dependencies.| Check the test suite file for problems, compatibility issues, and missing dependencies, then upload it again. |
|Failed to fetch runner class for test extraction. Please recheck your test suite.| Test discovery failed. The system couldn't extract test cases or classes from the provided runner application. This might be due to issues with the runner app itself or its configuration.| Check the test suite app and its configuration, then upload it again. |
|Failed to extract classes or tests from runner app - test discovery failed.| Test discovery failed. The system couldn't extract test cases or classes from the provided runner application. This might be due to issues with the runner app itself or an incompatibility with the testing framework used. | Check the test suite app and that it works with your testing framework, then upload it again. |
|No tests found in the test suite. Please check your test suite or applied filters.| The test execution framework couldn't locate any test cases to run due to: <br /> <b>Empty Test Suite: </b>Ensure your test suite contains at least one test class with a @Test annotated method.<br /> <b>Incorrect Filtering: </b>Verify that any applied test filters aren't accidentally excluding all tests. You can see more on espresso test filtering [here](/support/docs/speedup-espresso/).| Add at least one `@Test` method, and check that your filters do not exclude every test. |
|Tests could not be run as localization setup failed. Please check locale and try again.| The test suite encountered a localization setup error. This means the system's locale or language settings could not be configured correctly. Please verify your locale settings and try re-running the tests. | Check your locale settings, then run the tests again. |
|Oops! An error occurred at our end. Please try again.| A temporary infrastructure issue arose. While a device was allocated for your test, it became unavailable before the test execution started. Please retry the test. | Run the test again. If it keeps happening, contact support@testmuai.com. |
|Desired Capabilities Error. Please check the desired capabilities that you have passed.| The test encountered a [`Desired Capabilities`](/support/docs/espresso-supported-capabilities/) Error. This indicates an issue with the configuration provided for the test execution. Please verify the values you have set for desired capabilities like device, platform, or application path. | Check the device, platform, and application path values against the [supported capabilities](/support/docs/espresso-supported-capabilities/). |
| Oops! An error occurred at our end. Please try again. | An internal error occurred while retrieving configuration details for the test execution environment (HyperExecute API). A temporary glitch might be preventing communication with the API. Please retry the test execution. If the issue persists, contact support for further assistance. | Run the test again. If it keeps happening, contact support@testmuai.com. |
|Build has been stopped. | The build process was terminated prematurely. User intervention caused this stoppage, likely due to errors encountered during the build phase. | Check why the build was stopped, then run it again. |
|Build breached queue timeout| The test execution encountered a "Build breached queue timeout" error. This indicates the build exceeded the maximum allowed wait time while in a queue. This could be due to high system load or insufficient resources on the <BrandName /> platform. | Run the build again. |

## Next Steps
---

Continue with these related guides:

- [Getting started with Espresso testing](/support/docs/getting-started-with-espresso-testing/)
- [Espresso automation capabilities](/support/docs/espresso-supported-capabilities/)
- [Speed up your Espresso tests with filtering](/support/docs/speedup-espresso/)
- [Sharding Espresso tests via HyperExecute](/support/docs/sharding-espresso-rd-hyperexecute/)

>
If you still have any questions for us, please feel free to let us know via our <span className="doc__lt" onClick={() => window.openLTChatWidget()}>**24X7 Chat Portal**</span> or mail us to support@testmuai.com

<nav aria-label="breadcrumbs">
<ul className="breadcrumbs">
Expand All @@ -229,12 +287,8 @@ If you still have any questions for us, please feel free to let us know via our
</li>
<li className="breadcrumbs__item breadcrumbs__item--active">
<span className="breadcrumbs__link">
Debugging Espresso Tests
How to Debug Espresso Tests on TestMu AI
</span>
</li>
</ul>
</nav>




Loading
Loading