Failed to start an Appium session, error was: Error: Bad app: /Path/to/your/application.app
Failed to start an Appium session, error was: Error: Bad app: /Path/to/your/application.app
Failed to start an Appium session, error was: Error: Bad app: /Path/to/your/application.appPhase
Description
The user has defined the app
desired capability which points to their local file system. This will not work on BitBar Testing Appium tests.
Resolution
Remove the app
desired capability from the test script or comment it out.
Not executed
Not executed
Not executedDescription
The run was manually canceled by a user/admin.
Resolution
Contact the administrator.
Timeout for running tests exceeded
Timeout for running tests exceeded
Timeout for running tests exceededPhase
Description
This might be a pop-up or another application preventing the test execution.
Resolution
Test run failed to complete. Expected 14 tests received 0
Test run failed to complete. Expected 14 tests received 0
Test run failed to complete. Expected 14 tests received 0Description
The test run execution was started for 14 tests, but there are no results for any tests or some specific tests. This typically happens because the application crashed before all the tests were executed.
Instrumentation run failed due to ‘process crashed’
Instrumentation run failed due to ‘process crashed’
Instrumentation run failed due to ‘process crashed’Description
Typically, it is a device- or instrumentation-related problem. The process crashed for some unknown reason. The best way to find this reason is to check the device logcat and find the moment when it happens.
Instrumentation run failed due to android.content.ActivityNotFoundException
Instrumentation run failed due to android.content.ActivityNotFoundException
Instrumentation run failed due to android.content.ActivityNotFoundExceptionDescription
Some activity expected by the test script was not found.
Resolution
Go to the logs to find out which activity was not found.
Timeout for running tests exceeded
Timeout for running tests exceeded
Timeout for running tests exceededDescription
The test execution took too long, and the run was killed by BitBar Testing.
Instrumentation timed out after 600 seconds
Instrumentation timed out after 600 seconds
Instrumentation timed out after 600 secondsPhase
Instrumentation run failed due to java.lang.NullPointerException
Instrumentation run failed due to java.lang.NullPointerException
Instrumentation run failed due to java.lang.NullPointerExceptionDescription
This usually means some variable or object in the test is null.
Resolution
Inspect the stack trace to find the error and fix it.
Instrumentation run failed due to java.lang.ClassNotFoundException
Instrumentation run failed due to java.lang.ClassNotFoundException
Instrumentation run failed due to java.lang.ClassNotFoundExceptionDescription
This happens because of a bad .apk
build.
Resolution
Rebuild your application and try again.
Not executed
Not executed
Not executedDescription
The run was manually canceled by a user/admin.
Excluded
Excluded
ExcludedDescription
The device run was not executed because of API level requirements or the "first available device only" scheduling mode was selected when creating the test run. In this case, the test run is executed on the first available device, and others are excluded.
Timeout for running tests exceeded
Timeout for running tests exceeded
Timeout for running tests exceededDescription
This might be a pop-up or another application preventing the test execution.
Resolution
Server build has failed INSTALL_FAILED_INSUFFICIENT_STORAGE
Server build has failed INSTALL_FAILED_INSUFFICIENT_STORAGE
Server build has failed INSTALL_FAILED_INSUFFICIENT_STORAGEPhase
Description
No space in the device storage to install the application.
Resolution
Server build has failed [Failure [INSTALL_FAILED_ALREADY_EXISTS]]
Server build has failed [Failure [INSTALL_FAILED_ALREADY_EXISTS]]
Server build has failed [Failure [INSTALL_FAILED_ALREADY_EXISTS]]Phase
Description
For some reason, the application already exists on the device, and the reinstallation fails.
Resolution
Server build has failed [Failure [INSTALL_FAILED_UID_CHANGED]]
Server build has failed [Failure [INSTALL_FAILED_UID_CHANGED]]
Server build has failed [Failure [INSTALL_FAILED_UID_CHANGED]]Phase
Description
This is an Android error. According to Stack Overflow, /data/data/ has some trash files, and the installation fails.
Resolution
Unable to find instrumentation info for: ComponentInfo(com.example.android.apis.test/android.test.Instrumentation.Testrunner)
Unable to find instrumentation info for: ComponentInfo(com.example.android.apis.test/android.test.Instrumentation.Testrunner)
Unable to find instrumentation info for: ComponentInfo(com.example.android.apis.test/android.test.Instrumentation.Testrunner)Phase
Description
The test runner did not find test files.