> For the complete documentation index, see [llms.txt](https://docs.currents.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.currents.dev/guides.md). # Guides - [Record Key](https://docs.currents.dev/guides/record-key.md): Using record key to associate your runs with your organization - [Reporting](https://docs.currents.dev/guides/parallelization-guide.md) - [Reporting Strategy](https://docs.currents.dev/guides/parallelization-guide/reporting-strategy.md): How to structure and organize the reporting of CI test results to Currents - [CI Build ID](https://docs.currents.dev/guides/parallelization-guide/ci-build-id.md): Using CI Build ID for reporting to Currents - [Reporting in CI](https://docs.currents.dev/guides/parallelization-guide/playwright-sharding.md): Playwright Sharding and reporting the results to Currents - [Step-Level Reporting](https://docs.currents.dev/guides/parallelization-guide/step-level-reporting.md): Live test results: near-realtime streaming of step-level progress from CI machines - [Test Orchestration](https://docs.currents.dev/guides/test-orchestration.md): The better alternative to Playwright Sharding - [CI Optimization](https://docs.currents.dev/guides/ci-optimization.md): A guide on optimizing Playwright tests in CI for better efficiency - [Playwright Parallelization](https://docs.currents.dev/guides/ci-optimization/playwright-parallelization.md): A guide to Playwright Parallelization for speeding up Playwright tests in CI - [Orchestration Setup](https://docs.currents.dev/guides/ci-optimization/playwright-orchestration.md): Setup instructions for Playwright Orchestration - [Migration Guide](https://docs.currents.dev/guides/ci-optimization/playwright-orchestration/playwright-orchestration-migration-guide.md): Migration Guide for Currents Orchestration v1 -> v2 - [Orchestration (v1)](https://docs.currents.dev/guides/ci-optimization/playwright-orchestration/playwright-orchestration-v1.md): Playwright Orchestration Setup Guide for Currents v1 - [Fully Parallel Mode](https://docs.currents.dev/guides/ci-optimization/fully-parallel-mode.md): A guide on Playwright Fully Parallel mode - [Re-run Only Failed Tests](https://docs.currents.dev/guides/ci-optimization/re-run-only-failed-tests.md): A guide on rerunning only failed Playwright tests in CI - [Sharded runs](https://docs.currents.dev/guides/ci-optimization/re-run-only-failed-tests/re-run-only-failed-tests-sharded.md): Re-run only failed tests when using native Playwright sharding - [Orchestrated runs](https://docs.currents.dev/guides/ci-optimization/re-run-only-failed-tests/re-run-only-failed-tests-orchestrated-v2.md): Re-run only failed Playwright tests when using Currents Orchestration - [Cloud Spot Instances](https://docs.currents.dev/guides/ci-optimization/ci-tests-on-spot-instances.md): Running Playwright E2E tests on CI Spot Instances and using Currents Orchestration to automatically rerouting tests before an eviction. - [Failing Fast](https://docs.currents.dev/guides/ci-optimization/fail-fast-strategy.md): Fail-fast or cancelling runs on first failure - [Load Balancing](https://docs.currents.dev/guides/ci-optimization/load-balancing.md): Review of Orchestration strategies for Cypress and Playwright tests - [Code Coverage](https://docs.currents.dev/guides/coverage.md): Collect Code Coverage reports for web applications using Playwright or Cypress - [Code Coverage for Playwright](https://docs.currents.dev/guides/coverage/code-coverage-for-playwright.md): Learn how to enable Code Coverage reporting for Playwright - [Code Coverage for Cypress](https://docs.currents.dev/guides/coverage/code-coverage-for-cypress.md): Learn how to setup Cypress to start reporting code coverage results - [Currents Actions](https://docs.currents.dev/guides/currents-actions.md): Automate workflows by triggering actions based on flexible rules and conditions - [Setting up Currents Actions](https://docs.currents.dev/guides/currents-actions/setup-currents-actions.md): Setting up Current Actions for your Playwright Project - [Using Currents Actions](https://docs.currents.dev/guides/currents-actions/using-currents-actions.md): Create and Manage Currents Actions, trace action applications and outcomes - [Affected Tests](https://docs.currents.dev/guides/currents-actions/affected-tests.md): Track what tests have been affected by Actions - [Reference](https://docs.currents.dev/guides/currents-actions/reference.md): Currents Actions - condition, operations and actions reference documentation - [Conditions](https://docs.currents.dev/guides/currents-actions/reference/conditions.md): Reference documentation of Conditions that are available for Currents Actions - [Actions](https://docs.currents.dev/guides/currents-actions/reference/actions.md): Reference documentation for actions that apply as part for Currents Actions Engine - [Lifecycle Notifications](https://docs.currents.dev/guides/currents-actions/lifecycle-notifications.md): Configure and receive action lifecycle notifications - [Playwright Component Testing](https://docs.currents.dev/guides/playwright-component-testing.md): Using Currents with Playwright Component testing - [Playwright Visual Testing](https://docs.currents.dev/guides/playwright-visual-testing.md): Integrating Playwright Visual Comparison tools with Currents - including Argos, Percy and Applitools. - [Playwright Annotations](https://docs.currents.dev/guides/playwright-annotations.md): Using Playwright Annotations to enhance reporting to Currents dashboard - [Playwright Tags](https://docs.currents.dev/guides/playwright-tags.md): How to tag Playwright executions in Currents - [Environments](https://docs.currents.dev/guides/environments.md): How to label and filter Currents runs by environment (e.g. staging, production) - [Troubleshooting](https://docs.currents.dev/guides/troubleshooting-playwright.md): Troubleshooting Playwright integration with Currents --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.currents.dev/guides.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.