Connect & Get help from 6000+ developers on our Discord community.
Ask the Community
Ask the Community
BrowserStack Load Testing - Troubleshooting
Resolve common BrowserStack Load Testing issues and configuration errors quickly.
Use this page to troubleshoot common BrowserStack Load Testing issues and configuration problems.
Common issues and resolutions
Refer to the following table to diagnose and resolve common load test setup problems:
Selenium (Java/JUnit/TestNG)
| Issue | Remediation |
|---|---|
| Default source directory not found | If you do not override testSourceDirectory, BrowserStack expects tests under src/test/java. Confirm this path exists in the ZIP and that it contains your Java test files. |
Vanilla Java project includes test framework dependencyError: pom.xml contains TestNG/JUit dependencies - this is a TestNG project, not Selenium - Vanilla Java
|
If you run plain Java tests without TestNG or JUnit, remove any unused test framework dependencies from pom.xml to avoid configuration conflicts.Remove the TestNG/JUnit dependencies. |
| Test files not detected (ZIP root mismatch) | BrowserStack executes tests from the root of the uploaded ZIP. Update your configuration so that all test paths are relative to the ZIP root and re-upload the archive. |
| No TestNG dependency | Your pom.xml is present, but it does not include the TestNG dependencies. Add the appropriate test framework dependency and upload the updated project.TestNG dependency list: ["testng", "org.testng"]
|
| No JUnit dependency | Your pom.xml is present, but it does not include the JUnit dependencies. Add the appropriate test framework dependency and upload the updated project.JUnit dependency list: ["junit","junit-jupiter-api","junit-jupiter-engine","org.junit","org.junit.jupiter"]
|
Source directory not found (custom testSourceDirectory) |
If you use a custom <testSourceDirectory> in your Maven pom.xml under the <build> section, verify that the path exists in the uploaded ZIP and contains your .java test files. Following is an example pom.xml snippet:build <testSourceDirectory>src/ui-tests/java</testSourceDirectory>buildThe critical requirement is that the path specified in <testSourceDirectory> exists and includes at least one .java file; otherwise, Maven does not pick up the tests. |
Playwright
| Issue | Remediation |
|---|---|
Test files not detected (testDir not pointing to tests) |
Verify that the testDir path in your Playwright configuration points to the folder inside the ZIP that contains your test files. |
Test files not detected (testMatch pattern) |
Check that the testMatch pattern in your Playwright configuration matches your test file names and extensions so BrowserStack can discover them. |
| Test files not detected (ZIP root mismatch) | BrowserStack executes tests from the root of the uploaded ZIP. Update your configuration so that all test paths are relative to the ZIP root and re-upload the archive. |
| Test files excluded by configuration | Review any exclude patterns in your configuration and make sure at least one test file is not excluded so BrowserStack can find and run your tests. |
Nightwatch
| Issue | Remediation |
|---|---|
Test files not detected (src_folders not set) |
Set src_folders in your Nightwatch configuration to a directory that exists in the ZIP and contains your test files. |
| Test files excluded by configuration | Review any exclude patterns in your configuration and make sure at least one test file is not excluded so BrowserStack can find and run your tests. |
| Test files not detected (ZIP root mismatch) | BrowserStack executes tests from the root of the uploaded ZIP. Update your configuration so that all test paths are relative to the ZIP root and re-upload the archive. |
WebdriverIO
| Issue | Remediation |
|---|---|
Test files not detected (specs not set) |
Set specs in your WebdriverIO configuration to a directory that exists in the ZIP and contains your test files. |
| Test files excluded by configuration | Review any exclude patterns in your configuration and make sure at least one test file is not excluded so BrowserStack can find and run your tests. |
| Test files not detected (ZIP root mismatch) | BrowserStack executes tests from the root of the uploaded ZIP. Update your configuration so that all test paths are relative to the ZIP root and re-upload the archive. |
Python
| Issue | Remediation |
|---|---|
| Target file not found (Python) | Ensure that your ZIP includes the configured target test file and that it exists with a .py extension, as this file is the entry point for running your Python tests. |
| Test files not detected (ZIP root mismatch) | BrowserStack executes tests from the root of the uploaded ZIP. Update your configuration so that all test paths are relative to the ZIP root and re-upload the archive. |
Generic errors
| Issue | Remediation |
|---|---|
| Third-party connectors are added | If you use third-party connectors and tests fail to start or behave unexpectedly, contact BrowserStack Support with your test run ID and configuration details. |
| Test fails with Sync Failed | If the test fails with a Sync Failed error, contact BrowserStack Support and share the test run ID and logs so the team can investigate. |
| Tests are stuck in initialization | If tests remain in the initialization state for an extended period, contact BrowserStack Support with your configuration and test run ID for further analysis. |
| Tests ran but no data generated | If tests appear to run but no metrics are generated, contact BrowserStack Support so the team can review your configuration, logs, and network connectivity. |
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!