description |
---|
Troubleshooting Currents integration with Cypress |
{% hint style="warning" %} We are suspending our support of Cypress test runner version 13+
We will continue to support prior versions of Cypress.
Read more {% endhint %}
If you are experiencing issues with using @currents/cli
or cypress-cloud
, please submit a support request either via in-app support chat or on GitHub:
Please collect the following information to help us effectively debug the problem:
- The associated dashboard run URL
- Screenshots if applicable
- The exact command used to run
currents
orcypress-cloud
- Configuration files (
cypress.config.{jt}s
andcurrents.config.js
) - CI environment information (use the command below)
npx envinfo --system --binaries --browsers --npmPackages --duplicates --npmGlobalPackages
- Activate debug mode and collect the logs
{% hint style="info" %} Please capture and share the whole debug log - that will help the support person identify the root cause faster {% endhint %}
Starting from version 1.9.0 cypress-cloud
provides a CLI flag for activating the debug mode.
npx cypress-cloud run ... --cloud-debug
You can specify the scope of debug messages printed
true | all
show all debug messagescypress
activate debug mode for cypress onlycurrents
activate the debug mode for currents onlycommit-info
activate the debug mode for git commit info only
{% tabs %} {% tab title="cypress-cloud" %}
# on Linux
DEBUG=currents:*,cypress:* npx cypress-cloud run ...
# on Windows
cmd /V /C "set DEBUG=currents:*,cypress:*&& npx cypress-cloud run ..."
{% endtab %}
{% tab title="@currents/cli" %}
# on Linux
DEBUG=cy2*,cypress:* npx currents run ...
# on Windows
cmd /V /C "set DEBUG=cy2*,cypress:*&& npx currents run ..."
{% endtab %} {% endtabs %}