Skip to main content
Transform your testing process with: Real Device Features, Company-wide Licences, & Test Observability

Troubleshooting Cypress errors

Learn about the different types of errors and how to handle them.

While running the Cypress tests on BrowserStack, you may face majorly three types of errors:

  1. Errors while submitting tests to BrowserStack
  2. Errors while initiating the build runs on BrowserStack
  3. Errors while running Cypress tests on our browsers

Build submission errors

Type of error Probable cause Pointers for resolution
JSON errors: The CLI throws JSON parsing errors when there are errors in the JSON JSON formatting could be incorrect. Verify the JSON file in a JSON formatter.
Validation errors: the CLI throws validation errors when wrong values are passed in the CLI args or wrong capabilities mentioned in the browserstack.json file Incorrect CLI args or invalid capabilities in the browserstack.json file. Verify the CLI args and inspect the JSON file for incorrect or unsupported capabilities, such as browsers, test file paths, or timeouts.
Authentication errors Incorrect username or access key. Specify the correct user name and access key, referring to your Account settings.
Build acceptance errors You might have exhausted access to run tests on Automate, could be out of free-trial credits, or you’re out of parallels while running the tests. Verify your plan details in the Account settings.

Build run errors

Type of error Probable cause Pointers for resolution
Cypress configuration errors Incorrect path in the cypress_config_file option. Provide an accurate path in the cypress_config_file. option.
Application server errors Application server is not reachable by the tests. Ensure that your application server is available before you trigger your tests.
Missing plugin files One or more support files or plugins are missing or invalid. Ensure all plugins are available. Reinstall invalid plugins.
Missing NPM packages NPM packages aren’t installed before running the tests. Use the npm_dependencies option to list out all the required NPM packages. Install any missing package.

Test run errors

If there are any errors while your tests are running, you’d see those exact errors in the Automate dashboard, and you can update or retry your tests as required.

You can reach out to our Support team in case you need any help.

Note: Browserstack does not allow the execution of cy.task on Windows machines due to security concerns.

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

Is this page helping you?

Yes
No

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!

Talk to an Expert
Download Copy