Connect & Get help from fellow developers on our Discord community.
Ask the Community
Ask the Community
SDK error codes
Reference list of SDK error codes returned with meanings and suggested fixes.
When you run tests using BrowserStack SDKs, you might encounter error codes that indicate issues with your test execution. This page helps you quickly identify and resolve these errors by providing detailed explanations and actionable fixes for each error code.
How to use this page
- Locate the error code shown in your test logs.
- Read the meaning to understand the root cause.
- Apply the suggested fix and rerun your test.
Error code reference
| Error Code | Description |
|---|---|
| SDK-TRA-001 | The build run appears to be on vanilla Java (generic runner without a supported test framework detected). We currently do not support test reporting for vanilla Java build runs. |
| SDK-TRA-002 | An invalid or unsupported test framework was detected. In such cases, you might notice builds with no tests reported. |
|
SDK-TRA-003 SDK-TRA-004 SDK-TRA-006 |
The test process was interrupted midway which leads to inconsistencies in the test reporting. |
|
SDK-TRA-005 |
The test process was interrupted midway which leads to inconsistencies in the test reporting. Tests might not be visible on the BrowserStack dashboard because we could not find the relevant test framework classes in your project classpath. Tests might not be visible on the BrowserStack dashboard because we could not find the Cucumber dependency in your system classpath. Tests might not be visible on the BrowserStack dashboard because the Cucumber dependency installed with your project is not supported. |
We're sorry to hear that. Please share your feedback so we can do better
Contact our Support team for immediate help while we work on improving our docs.
We're continuously improving our docs. We'd love to know what you liked
We're sorry to hear that. Please share your feedback so we can do better
Contact our Support team for immediate help while we work on improving our docs.
We're continuously improving our docs. We'd love to know what you liked
Thank you for your valuable feedback!