Android

If you encounter problems, you can always ask questions in the chat with developers.

Here is the list of known Android test problems and ways to solve them.

"Closed" or "device offline"

If you faced error with description closed or device offline then try to increase workers resources (such as CPU, for example).

This kind of error can occur when there is not enough resources for workers.

Parameterized test do not launch or do not produce results

For now we do not support parameterized tests with name parameter. For example, @Parameterized.Parameters(name = "parameterized test name").

If you want this test works try to remove name parameter. For example, @Parameterized.Parameters.

Applications installation timeout on Android API 27

Sometimes apk doesn't install within the timeout period. Try to increase application installation timeout or Emcee worker resources, or try to use another Android API level.

If Allure's report is missing tests

If you can't find some tests in Allure report try to add @RunWith(AllureAndroidJUnit4::class) annotation to the test class with missed tests.