For the complete documentation index, see llms.txt. This page is also available as Markdown.

Troubleshooting

Troubleshooting Playwright integration with Currents

If you are experiencing issues with using @currents/playwright, enable debug mode to collect more information about the failure and submit a support request via our support channels.

TL;DR share the following information

Collect environment information

  • Package Versions

  • Currents Run ID or Dashboard URL associated with the issue

  • Screenshots or video recordings if applicable

  • Full error message, including the stack trace, if available

  • Full and relevant CI execution logs with sensitive information redacted

  • CI pipeline configuration

    • The exact commands used during the execution

    • Relevant configuration of the CI setup stages

Collect and share the debug logs

  • npx pwc --pwc-debug=full ... OR

  • npx pwc-p --pwc-debug=remote ... OR

  • DEBUG=currents* playwright test ...

1. Collecting Environment Information

Please collect the following information to help us effectively debug the problem:

  • The associated dashboard Run URL

  • Screenshots if applicable

  • Your setup method and configuration files

  • The exact command used to run playwright

  • Environment information (use the command below)

Use the following command to print information about your CI environment

2. Activate Debug Mode

@currents/playwright simplifies collecting the debug information by automatically uploading the logs to Currents.

To enable uploading the debug logs:

  • For pwc command-line executable run pwc --pwc-debug=full OR

  • For pwc-p run pwc-p --pwc-debug=full OR

  • Set environment variable DEBUG=currents* playwright test...

--pwc-debug enables uploading the debug logs to our servers (see pwc-p run documentation):

  • remote uploads the debug logs to Currents servers;

  • full prints the logs to stdout and also upload them to Currents.

For example:

When enabled, the debug logs will be uploaded to Currents servers and a confirmation message will be shown after the run's completion, for example:

Remote debug logs notification example

Currents displays a link to the CI job/run where the tests were executed. If this link is missing or incorrect:

Possible causes:

  1. Auto-detection failed — Your CI provider environment variables are not available in the test environment (e.g., inside a Docker container, custom runner, or self-hosted CI)

  2. Custom CI system — Your CI provider is not automatically recognized by Currents

  3. URL override needed — You need to manually specify the CI URL

Solution:

Set the CURRENTS_CI_URL environment variable to provide the correct CI job/run URL:

For more details on CURRENTS_CI_URL, see Configuration.

Last updated

Was this helpful?