# Currents > Currents is the best Playwright reporter, dashboard and test orchestrator engineered to optimize complex test suites for health, reliability, and performance. ## Website - [Pricing](https://currents.dev/pricing) - [Migrate from Cypress to Playwright](https://currents.dev/cypress-to-playwright) - [Case Studies](https://currents.dev/case-studies) ## Documentation - [Playwright | Currents Documentation](https://docs.currents.dev/getting-started/playwright) - [Playwright: Quick Start | Currents Documentation](https://docs.currents.dev/getting-started/playwright/you-first-playwright-run): Running Playwright tests with Currents Dashboard - [Troubleshooting Playwright | Currents Documentation](https://docs.currents.dev/getting-started/playwright/troubleshooting-playwright): Troubleshooting Playwright integration with Currents - [Currents vs Others | Currents Documentation](https://docs.currents.dev/getting-started/playwright/currents-vs-others): How to chose the best Playwright Reporter - [Cypress | Currents Documentation](https://docs.currents.dev/getting-started/cypress) - [Your First Cypress Run | Currents Documentation](https://docs.currents.dev/getting-started/cypress/you-first-cypress-run): Running Cypress tests in parallel with Currents Dashboard - [Integrating with Cypress | Currents Documentation](https://docs.currents.dev/getting-started/cypress/integrating-with-cypress): Overview of tools available for integrating cypress with Currents or Sorry Cypress - [Compatibility | Currents Documentation](https://docs.currents.dev/getting-started/cypress/integrating-with-cypress/compatibility): Integrating Cypress with Currents - compatibility table - [Alternative Cypress Binaries | Currents Documentation](https://docs.currents.dev/getting-started/cypress/integrating-with-cypress/alternative-cypress-binaries): Using alternative Cypress Binaries - [Troubleshooting Cypress | Currents Documentation](https://docs.currents.dev/getting-started/cypress/troubleshooting-cypress): Troubleshooting Currents integration with Cypress - [Jest | Currents Documentation](https://docs.currents.dev/getting-started/jest) - [Your First Jest Run | Currents Documentation](https://docs.currents.dev/getting-started/jest/your-first-jest-run): Running Jest tests with Currents dashboard - [Detox + Jest | Currents Documentation](https://docs.currents.dev/getting-started/jest/detox-+-jest): Follow this guide to enable integrating Detox + Jest with Currents - [Troubleshooting Jest | Currents Documentation](https://docs.currents.dev/getting-started/jest/troubleshooting): Troubleshooting Jest integration with Currents - [Others | Currents Documentation](https://docs.currents.dev/getting-started/others): Integrate Currents with any framework by using JUnit compatible XML reporters - [CI Setup | Currents Documentation](https://docs.currents.dev/getting-started/ci-setup): Learn how to integrate Currents with your CI provider. - [GitHub Actions | Currents Documentation](https://docs.currents.dev/getting-started/ci-setup/github-actions): Running Playwright and Cypress tests in parallel with GitHub Actions and Currents dashboard - [Cypress - GitHub Actions | Currents Documentation](https://docs.currents.dev/getting-started/ci-setup/github-actions/cypress-github-actions): Using GitHub Actions Matrix for parallelizing Cypress tests - [Playwright - GitHub Actions | Currents Documentation](https://docs.currents.dev/getting-started/ci-setup/github-actions/playwright-github-actions): Running Playwright tests in Parallel in GitHub Actions using Matrix Workflow - [Jest - GitHub Actions | Currents Documentation](https://docs.currents.dev/getting-started/ci-setup/github-actions/jest-github-actions): Running Jest in Parallel on GitHub Actions using Matrix Workflow - [Node.js - GitHub Actions | Currents Documentation](https://docs.currents.dev/getting-started/ci-setup/github-actions/node-github-actions): Running Node.js Tests on GitHub Actions - [Commit data for GitHub Actions | Currents Documentation](https://docs.currents.dev/getting-started/ci-setup/github-actions/commit-data-for-github-actions): How to get correct git commit information when using GitHub Actions - [Custom Docker runners | Currents Documentation](https://docs.currents.dev/getting-started/ci-setup/github-actions/custom-docker-runners): Self hosted/managed docker runners - [Named Runners | Currents Documentation](https://docs.currents.dev/getting-started/ci-setup/github-actions/named-runners): Github Actions provides the ability to use human-readable runner names, and Currents displays these in the dashboard, allowing you to see which runner executed each spec file. - [GitLab | Currents Documentation](https://docs.currents.dev/getting-started/ci-setup/gitlab): Running Cypress and Playwright tests in parallel on Gitlab CI/CD - [Cypress - GitLab CI/CD | Currents Documentation](https://docs.currents.dev/getting-started/ci-setup/gitlab/cypress-gitlab-ci-cd): Running Cypress test in parallel on GitLab - [Playwright - GitLab CI/CD | Currents Documentation](https://docs.currents.dev/getting-started/ci-setup/gitlab/playwright-gitlab-ci-cd): Running Playwright test in parallel using GitLab CI/CD - [Custom Docker runners | Currents Documentation](https://docs.currents.dev/getting-started/ci-setup/gitlab/custom-docker-runners): Self hosted/managed docker runners - [Jenkins | Currents Documentation](https://docs.currents.dev/getting-started/ci-setup/jenkins) - [Cypress - Jenkins | Currents Documentation](https://docs.currents.dev/getting-started/ci-setup/jenkins/cypress-jenkins): Running Cypress tests in parallel with Jenkins and Currents Dashboard - [Playwright - Jenkins | Currents Documentation](https://docs.currents.dev/getting-started/ci-setup/jenkins/jenkins-playwright): Running Playwright tests in parallel with Jenkins and Currents Dashboard - [CircleCI | Currents Documentation](https://docs.currents.dev/getting-started/ci-setup/circleci): Run Cypress and Playwright test in parallel on CircleCI - [Cypress - CircleCI | Currents Documentation](https://docs.currents.dev/getting-started/ci-setup/circleci/cypress-circleci): Running Cypress tests in parallel on CircleCI and Currents dashboard - [Playwright - CircleCI | Currents Documentation](https://docs.currents.dev/getting-started/ci-setup/circleci/playwright-circleci): Running Playwright Tests in Parallel on CircleCI and Currents - [Bitbucket | Currents Documentation](https://docs.currents.dev/getting-started/ci-setup/bitbucket) - [Cypress - Bitbucket Pipelines | Currents Documentation](https://docs.currents.dev/getting-started/ci-setup/bitbucket/cypress-bitbucket-pipelines): Running Cypress tests in parallel on Bitbucket Pipelines and Currents dashboard - [Azure DevOps | Currents Documentation](https://docs.currents.dev/getting-started/ci-setup/azure-devops): Running Cypress and Playwright tests in parallel in Azure DevOps and Currents Dashboard - [Cypress - Azure DevOps | Currents Documentation](https://docs.currents.dev/getting-started/ci-setup/azure-devops/cypress-azure-devops): Running Cypress test in parallel on Azure DevOps and Currents Dashboard - [Playwright - Azure DevOps | Currents Documentation](https://docs.currents.dev/getting-started/ci-setup/azure-devops/playwright-azure-devops): Running Playwright test in parallel on Azure DevOps and Currents Dashboard - [AWS Code Build | Currents Documentation](https://docs.currents.dev/getting-started/ci-setup/aws-code-build): Running cypress tests in parallel on AWS Code Build and Currents dashboard - [Cypress - AWS Code Build | Currents Documentation](https://docs.currents.dev/getting-started/ci-setup/aws-code-build/cypress-aws-code-build): Running Cypress in parallel on AWS CodeBuild - [Playwright - AWS Code Build | Currents Documentation](https://docs.currents.dev/getting-started/ci-setup/aws-code-build/playwright-aws-code-build): Running Playwright Tests in Parallel on AWS CodeBuild and Currents - [NX | Currents Documentation](https://docs.currents.dev/getting-started/ci-setup/nx): Executing Currents runs in a NX workspace - [Playwright - NX | Currents Documentation](https://docs.currents.dev/getting-started/ci-setup/nx/playwright-nx): Running Playwright tests with NX - [Cypress - NX | Currents Documentation](https://docs.currents.dev/getting-started/ci-setup/nx/cypress-nx): Running Cypress tests with NX ## Guides - [Record Key | Currents Documentation](https://docs.currents.dev/guides/record-key): Using record key to associate your runs with your organization - [CI Build ID | Currents Documentation](https://docs.currents.dev/guides/ci-build-id): Using CI Build ID for reporting to Currents - [Reporting | Currents Documentation](https://docs.currents.dev/guides/parallelization-guide) - [Reporting Strategy | Currents Documentation](https://docs.currents.dev/guides/parallelization-guide/reporting-strategy): How to structure and organize the reporting of CI test results to Currents - [Reporting in CI | Currents Documentation](https://docs.currents.dev/guides/parallelization-guide/playwright-sharding): Playwright Sharding and reporting the results to Currents - [Step-Level Reporting | Currents Documentation](https://docs.currents.dev/guides/parallelization-guide/step-level-reporting): Live test results: near-realtime streaming of step-level progress from CI machines - [CI Optimization | Currents Documentation](https://docs.currents.dev/guides/ci-optimization): A guide on optimizing Playwright tests in CI for better efficiency - [Playwright Parallelization | Currents Documentation](https://docs.currents.dev/guides/ci-optimization/playwright-parallelization): A guide to Playwright Parallelization for speeding up Playwright tests in CI - [Orchestration Setup | Currents Documentation](https://docs.currents.dev/guides/ci-optimization/playwright-orchestration): Playwright Orchestration setup instructions - [Fully Parallel Mode | Currents Documentation](https://docs.currents.dev/guides/ci-optimization/fully-parallel-mode): A guide on Playwright Fully Parallel mode - [Re-run Only Failed Tests | Currents Documentation](https://docs.currents.dev/guides/ci-optimization/re-run-only-failed-tests): A guide on rerunning only failed Playwright tests in CI - [Cloud Spot Instances | Currents Documentation](https://docs.currents.dev/guides/ci-optimization/ci-tests-on-spot-instances): Running Playwright E2E tests on CI Spot Instances and using Currents Orchestration to automatically rerouting tests before an eviction. - [Failing Fast | Currents Documentation](https://docs.currents.dev/guides/ci-optimization/fail-fast-strategy): Fail-fast or cancelling runs on first failure - [Load Balancing | Currents Documentation](https://docs.currents.dev/guides/ci-optimization/load-balancing): Review of Orchestration strategies for Cypress and Playwright tests - [Code Coverage | Currents Documentation](https://docs.currents.dev/guides/coverage): Collect Code Coverage reports for web applications using Playwright or Cypress - [Code Coverage for Playwright | Currents Documentation](https://docs.currents.dev/guides/coverage/code-coverage-for-playwright): Learn how to enable Code Coverage reporting for Playwright - [Code Coverage for Cypress | Currents Documentation](https://docs.currents.dev/guides/coverage/code-coverage-for-cypress): Learn how to setup Cypress to start reporting code coverage results - [Currents Actions | Currents Documentation](https://docs.currents.dev/guides/currents-actions): Automate workflows by triggering actions based on flexible rules and conditions - [Setup Currents Actions | Currents Documentation](https://docs.currents.dev/guides/currents-actions/setup-currents-actions): Setting up Current Actions for your Playwright Project - [Using Currents Actions | Currents Documentation](https://docs.currents.dev/guides/currents-actions/using-currents-actions): Create and Manage Currents Actions, trace action applications and outcomes - [Reference | Currents Documentation](https://docs.currents.dev/guides/currents-actions/reference): Currents Actions - condition, operations and actions reference documentation - [Conditions | Currents Documentation](https://docs.currents.dev/guides/currents-actions/reference/conditions): Reference documentation of Conditions that are available for Currents Actions - [Actions | Currents Documentation](https://docs.currents.dev/guides/currents-actions/reference/actions): Reference documentation for actions that apply as part for Currents Actions Engine - [Playwright Component Testing | Currents Documentation](https://docs.currents.dev/guides/playwright-component-testing): Using Currents with Playwright Component testing - [Playwright Visual Testing | Currents Documentation](https://docs.currents.dev/guides/playwright-visual-testing): Integrating Playwright Visual Comparison tools with Currents - including Argos, Percy and Applitools. - [Playwright Annotations | Currents Documentation](https://docs.currents.dev/guides/playwright-annotations): Using Playwright Annotations to enhance reporting to Currents dashboard - [Playwright Tags | Currents Documentation](https://docs.currents.dev/guides/playwright-tags): How to tag Playwright executions in Currents - [MCP Server | Currents Documentation](https://docs.currents.dev/guides/mcp-server): Connect AI Agents to Currents ## Dashboard - [Projects | Currents Documentation](https://docs.currents.dev/dashboard/projects) - [Projects Summary view | Currents Documentation](https://docs.currents.dev/dashboard/projects/projects-summary-view): Customize how you visualize projects on the Projects page - [Project Settings | Currents Documentation](https://docs.currents.dev/dashboard/projects/project-settings): Fine-tune your project settings - [Archive and Unarchive Projects | Currents Documentation](https://docs.currents.dev/dashboard/projects/archive-and-unarchive-projects): Feature to better manage and visualize projects - [Runs | Currents Documentation](https://docs.currents.dev/dashboard/runs) - [Run Status | Currents Documentation](https://docs.currents.dev/dashboard/runs/run-status): Details about different states that a Currents dashboard run can have - [Run Details | Currents Documentation](https://docs.currents.dev/dashboard/runs/run-details): Cypress and Playwright run details and metadata - git, environment, execution state - [Commit Information | Currents Documentation](https://docs.currents.dev/dashboard/runs/commit-information): Displaying Commit Information on Currents - [Tags | Currents Documentation](https://docs.currents.dev/dashboard/runs/tags): Using Tags in Currents Dashboard - [Run Timeouts | Currents Documentation](https://docs.currents.dev/dashboard/runs/run-timeouts): Understand tests timeouts and how to avoid them - [Cancelling Runs | Currents Documentation](https://docs.currents.dev/dashboard/runs/cancel-run): Cancelling Cypress and Playwright CI tests runs - [Deleting Runs | Currents Documentation](https://docs.currents.dev/dashboard/runs/deleting-runs): This feature allows you to permanently remove a run from our Dashboard - [Run Progress | Currents Documentation](https://docs.currents.dev/dashboard/runs/run-progress): Run progress view show the detailed distribution of your test on CI machines - [Tests | Currents Documentation](https://docs.currents.dev/dashboard/tests) - [Spec Files | Currents Documentation](https://docs.currents.dev/dashboard/tests/spec-file-status): Playwright Spec files status in Currents Dashboard - [Test Status | Currents Documentation](https://docs.currents.dev/dashboard/tests/test-status): Playwright and Cypress Test Status - detailed guide and explanation - [Flaky Tests | Currents Documentation](https://docs.currents.dev/dashboard/tests/flaky-tests): Guide to Playwright Flaky Tests - [Test History | Currents Documentation](https://docs.currents.dev/dashboard/tests/test-history): Explore historical Playwright and Cypress tests performance with Test History snipper - [Test Suite Explorer | Currents Documentation](https://docs.currents.dev/dashboard/test-suite-performance-explorer): Explore Test Suite Health and Performance with Currents Explorer - [Test Explorer | Currents Documentation](https://docs.currents.dev/dashboard/test-suite-performance-explorer/tests-explorer): Test Cases Health and Performance Dashboard - Flakiness, Failure Rate, Duration. - [Spec Files Explorer | Currents Documentation](https://docs.currents.dev/dashboard/test-suite-performance-explorer/spec-files-explorer): Spec-level Health and Performance Dashboard - Flakiness, Failure Rate, Duration, Suite Size - [Error Explorer | Currents Documentation](https://docs.currents.dev/dashboard/test-suite-performance-explorer/errors-explorer): Error Explorer helps to identify the most common errors that are affecting your testing suite. - [Reference | Currents Documentation](https://docs.currents.dev/dashboard/test-suite-performance-explorer/reference): How to read and use Test Explorer and Spec Files Explorer performance charts ## Automated-reports - [Automated Reports | Currents Documentation](https://docs.currents.dev/automated-reports): Proactively Detecting Test Performance Regressions ## Insights-and-analytics - [Insights and Analytics | Currents Documentation](https://docs.currents.dev/insights-and-analytics): Test and Run Insights and Analytics Guide ## Administration - [Administration | Currents Documentation](https://docs.currents.dev/administration) - [Email Domain Based Access | Currents Documentation](https://docs.currents.dev/administration/email-domain-based-access): Grant access to Currents Dashboard for the whole organization based on the email domain - [SSO SAML2.0 | Currents Documentation](https://docs.currents.dev/administration/sso-saml2.0): SSO SAML2.0 Instructions for Currents - [SAML2.0 Configuration | Currents Documentation](https://docs.currents.dev/administration/sso-saml2.0/saml2.0-configuration): Enabling SSO for Currents - manual SAML2.0 configuration - [SCIM User Provisioning | Currents Documentation](https://docs.currents.dev/administration/sso-saml2.0/scim-user-provisioning): Provision and de-provision users in Currents using SCIM v2 - [IdP-initiated Sessions | Currents Documentation](https://docs.currents.dev/administration/sso-saml2.0/idp-initiated-sessions): IdP-initiated sign-in sessions for Currents - [JumpCloud | Currents Documentation](https://docs.currents.dev/administration/sso-saml2.0/jumpcloud): Setting up SAML2.0 SSO with JumpCloud as an IdP for Currents - [JumpCloud User provisioning | Currents Documentation](https://docs.currents.dev/administration/sso-saml2.0/jumpcloud/jumpcloud-user-provisioning): Provision and de-provision users in Currents using JumpCloud - [Okta | Currents Documentation](https://docs.currents.dev/administration/sso-saml2.0/okta): Setting up SAML2.0 SSO with Okta as an IdP - Currents SSO - [Okta User provisioning | Currents Documentation](https://docs.currents.dev/administration/sso-saml2.0/okta/okta-user-provisioning): Provision and de-provision users in Currents using Okta - [Troubleshooting SSO | Currents Documentation](https://docs.currents.dev/administration/sso-saml2.0/troubleshooting-sso): Troubleshooting SSO connectivity to Currents - [Billing & Usage | Currents Documentation](https://docs.currents.dev/administration/billing-and-usage): Managing Billing and Subscription for your Organization ## Billing-and-pricing - [Billing and Pricing | Currents Documentation](https://docs.currents.dev/billing-and-pricing): How Currents Billing and Pricing Works ## Resources - [Reporters | Currents Documentation](https://docs.currents.dev/resources/reporters) - [cypress-cloud | Currents Documentation](https://docs.currents.dev/resources/reporters/cypress-cloud): Setup and usage instruction for cypress-cloud - [Batched Orchestration | Currents Documentation](https://docs.currents.dev/resources/reporters/cypress-cloud/batched-orchestration): Batched orchestration for cypress-cloud - [Migration to Cypress@13 | Currents Documentation](https://docs.currents.dev/resources/reporters/cypress-cloud/migration-to-cypress-13): Use cypress-cloud with Cypress@13 - [@currents/cli | Currents Documentation](https://docs.currents.dev/resources/reporters/currents-cli): Setup and usage instructions for Cypress integration with Currents Dashboard - [@currents/playwright | Currents Documentation](https://docs.currents.dev/resources/reporters/currents-playwright): Setup and usage instructions for Playwright integration with Currents Dashboard - [Configuration | Currents Documentation](https://docs.currents.dev/resources/reporters/currents-playwright/configuration): @currents/playwright configuration reference - [pwc | Currents Documentation](https://docs.currents.dev/resources/reporters/currents-playwright/pwc): pwc command-line executable documentation - [pwc-p (orchestration) | Currents Documentation](https://docs.currents.dev/resources/reporters/currents-playwright/pwc-p-orchestration): Currents orchestration pwc-p command-line executable documentation - [Playwright Fixtures | Currents Documentation](https://docs.currents.dev/resources/reporters/currents-playwright/playwright-fixtures): Enhance Playwright functionality with Currents fixtures for Playwright - [@currents/jest | Currents Documentation](https://docs.currents.dev/resources/reporters/currents-jest): Currents reporter for Jest - [@currents/node-test-reporter | Currents Documentation](https://docs.currents.dev/resources/reporters/currents-node-test-reporter): Currents Reporter for Node.js Testing Framework - [@currents/cmd | Currents Documentation](https://docs.currents.dev/resources/reporters/currents-cmd): The package has CLI commands and tools for Currents platform - [currents api | Currents Documentation](https://docs.currents.dev/resources/reporters/currents-cmd/currents-api): Learn how to get data from Currents API using currents api CLI command - [currents upload | Currents Documentation](https://docs.currents.dev/resources/reporters/currents-cmd/currents-upload): Learn how to upload test results to Currents using currents upload command - [currents cache | Currents Documentation](https://docs.currents.dev/resources/reporters/currents-cmd/currents-cache): Use currents cache command to store and retrieve data from Currents-managed remote cache - [currents convert | Currents Documentation](https://docs.currents.dev/resources/reporters/currents-cmd/currents-convert): CLI tool for converting reports from various formats to Currents-compatible format - [Data Format Reference | Currents Documentation](https://docs.currents.dev/resources/reporters/data-format-reference): Currents Reporting API - Data Format Reference - [Integrations | Currents Documentation](https://docs.currents.dev/resources/integrations) - [GitHub | Currents Documentation](https://docs.currents.dev/resources/integrations/github): Integrating GitHub with Currents dashboard for running Playwright tests - [GitHub App | Currents Documentation](https://docs.currents.dev/resources/integrations/github/github-app): Cypress and Playwright GitHub App integration for Currents dashboard - [GitHub OAuth | Currents Documentation](https://docs.currents.dev/resources/integrations/github/github-oauth) - [GitLab | Currents Documentation](https://docs.currents.dev/resources/integrations/gitlab): Integrating Currents dashboard with GitLab - [Slack | Currents Documentation](https://docs.currents.dev/resources/integrations/slack): Send Playwright and Cypress tests results to Slack - [Microsoft Teams | Currents Documentation](https://docs.currents.dev/resources/integrations/microsoft-teams): Send Cypress and Playwright tests results to Microsoft Teams - [HTTP Webhooks | Currents Documentation](https://docs.currents.dev/resources/integrations/http-webhooks): HTTP Webhooks for Playwright and Cypress tests dashboard - [Bitbucket | Currents Documentation](https://docs.currents.dev/resources/integrations/bitbucket): Send Cypress and Playwright tests results to Bitbucket - [Jira | Currents Documentation](https://docs.currents.dev/resources/integrations/jira): Connect Currents with Jira to create new or link existing issues in Jira without leaving Currents - [Setup | Currents Documentation](https://docs.currents.dev/resources/integrations/jira/setup): Setup instructions for Currents integration with Jira - [Usage | Currents Documentation](https://docs.currents.dev/resources/integrations/jira/usage): Learn how to use Currents Jira Integration - [API | Currents Documentation](https://docs.currents.dev/resources/api) - [Introduction | Currents Documentation](https://docs.currents.dev/resources/api/introduction): API Reference - access Currents data programmatically - [Authentication | Currents Documentation](https://docs.currents.dev/resources/api/authentication): API Reference - Authentication - [API Keys | Currents Documentation](https://docs.currents.dev/resources/api/api-keys): API Reference - managing API keys - [Errors | Currents Documentation](https://docs.currents.dev/resources/api/errors): API Reference - error codes and responses - [Pagination | Currents Documentation](https://docs.currents.dev/resources/api/pagination): API Reference - pagination and listing - [API Resources | Currents Documentation](https://docs.currents.dev/resources/api/api-resources): API Reference - list of available resources - [Projects | Currents Documentation](https://docs.currents.dev/resources/api/api-resources/projects): API Reference - Projects resource - [Runs | Currents Documentation](https://docs.currents.dev/resources/api/api-resources/runs): API Reference - Runs resource - [Instances | Currents Documentation](https://docs.currents.dev/resources/api/api-resources/instances): API Reference - Instance resource - [Test Results | Currents Documentation](https://docs.currents.dev/resources/api/api-resources/test-results): API Reference - Test Results - [Test Signature | Currents Documentation](https://docs.currents.dev/resources/api/api-resources/test-signature): API Reference - Test Signature resource - [Spec Files Explorer - API | Currents Documentation](https://docs.currents.dev/resources/api/api-resources/spec-files): API Reference - Spec Files resource - [Data Privacy | Currents Documentation](https://docs.currents.dev/resources/data-privacy) - [Access to Customer Data | Currents Documentation](https://docs.currents.dev/resources/data-privacy/access-to-customer-data): Overview of Customer Data that Currents collects during its execution - [Data Retention | Currents Documentation](https://docs.currents.dev/resources/data-privacy/data-retention): Retention periods for different types of data collected by Currents - [Cloud Endpoints | Currents Documentation](https://docs.currents.dev/resources/data-privacy/cloud-endpoints): A list of internet-facing Currents services and endpoints - [Support | Currents Documentation](https://docs.currents.dev/resources/support): Users guide for reporting support and troubleshooting issues with Currents systems ## Blog Posts - [Customer Success Story: Juvare](https://currents.dev/blog/currents-and-juvare) - [Human-in-the-Loop Testing: Best Practices to Combine AI and Human QA](https://currents.dev/blog/best-practices-to-combine-ai-and-human-qa) - [State of Playwright AI Ecosystem in 2026](https://currents.dev/blog/state-of-playwright-ai-ecosystem-in-2026) - [When Tests Should Run Headless vs Headed in Playwright](https://currents.dev/blog/when-tests-should-run-headless-vs-headed-in-playwright) - [9 Strategies to Get the Most Out of Playwright Test Agents](https://currents.dev/blog/9-strategies-to-get-the-most-out-of-playwright-test-agents) - [Customer Success Story: Kittl](https://currents.dev/blog/currents-and-kittl) - [Playwright MCP: What It Is, How It Works, and When It’s Worth Using](https://currents.dev/blog/playwright-mcp) - [AI Skill: Playwright Best Practices](https://currents.dev/blog/playwright-best-practices-skill) - [How To Debug Playwright Tests in CI: The Complete Guide](https://currents.dev/blog/how-to-debug-playwright-tests-in-ci) - [Customer Success Story: n8n](https://currents.dev/blog/currents-and-n8n) - [How To Adopt Playwright the Right Way](https://currents.dev/blog/how-to-adopt-playwright-the-right-way) - [How To Speed Up Playwright Tests: 7 Tips From Experts](https://currents.dev/blog/how-to-speed-up-playwright-tests) - [How To Measure Code Coverage in Playwright Tests](https://currents.dev/blog/how-to-measure-code-coverage-in-playwright-tests) - [Optimizing Test Runtime: Playwright Sharding vs. Workers](https://currents.dev/blog/optimizing-test-runtime-playwright-sharding-vs-workers) - [How To Build Reliable Playwright Tests: A Cultural Approach](https://currents.dev/blog/how-to-build-reliable-playwright-tests-a-cultural-approach) - [How to Run Playwright Tests Without the Pain: 14 Lessons Learned after 500+ Tests](https://currents.dev/blog/how-to-run-playwright-tests-without-the-pain) - [How to Track the Health of Your Playwright Test Suite](https://currents.dev/blog/how-to-track-the-health-of-your-playwright-test-suite) - [What Is a Flaky Test in Software Testing, and How to Fix It](https://currents.dev/blog/what-is-a-flaky-test-and-how-to-fix-it) - [Debugging Playwright Timeouts: A Practical Checklist](https://currents.dev/blog/debugging-playwright-timeouts) - [AWS us-east-1 Outage Report](https://currents.dev/blog/us-east-1-incident) - [Alternative to Microsoft Playwright Workspaces](https://currents.dev/blog/microsoft-workspaces-vs-currents) - [Best Playwright Tools to Supercharge Your Testing in 2025](https://currents.dev/blog/best-playwright-tools-to-supercharge-your-testing-in-2025) - [Case Study: Hover](https://currents.dev/blog/currents-and-hover) - [Alternative to DataDog for Playwright Testing](https://currents.dev/blog/datadog-vs-currents) - [Alternative to LambdaTest for Playwright Testing](https://currents.dev/blog/lambdatest-vs-currents) - [Alternative to ReportPortal for Playwright Testing](https://currents.dev/blog/reportportal-vs-currents) - [Introducing Currents MCP Server](https://currents.dev/blog/currents-mcp) - [Alternative to BrowserStack for Playwright Testing](https://currents.dev/blog/browserstack-vs-currents) - [70% CI costs reduction by running Playwright Tests on Spot Instances](https://currents.dev/blog/currents-and-fundguard) - [Alternative to Microsoft Playwright Testing](https://currents.dev/blog/microsoft-vs-currents) - [Currents Achieves SOC 2 Type 2 Certification](https://currents.dev/blog/currents-soc2-type2) - [Alternative to Allure Report for Playwright Testing](https://currents.dev/blog/allure-vs-currents) - [Company Update - January 2025](https://currents.dev/blog/jan-2025-update) - [Currents Achieves SOC 2 Type 1 Certification](https://currents.dev/blog/currents-soc2-type1) - [From Cypress to Playwright - cost, migration steps, timeline and AI tools](https://currents.dev/blog/cypress-to-playwright-migration) - [Cypress vs Playwright for tech leaders: cost and risks analysis](https://currents.dev/blog/cypress-playwright-for-tech-leaders) - [Cypress vs Playwright - Flakiness Analysis](https://currents.dev/blog/cypress-vs-playwright-flakiness-comparison) - [Currents Update - May 2024](https://currents.dev/blog/may-2024-update) - [Case Study: Ramp Network](https://currents.dev/blog/currents-and-ramp) - [Customer Success Story: Runa.io](https://currents.dev/blog/currents-and-runa) - [Playwright Reporter for Currents v1.0.0 ✨](https://currents.dev/blog/playwright-reporter-1.0.0) - [Case Study: Firstbase](https://currents.dev/blog/currents-and-firstbase) - [Case Study: Business Insider](https://currents.dev/blog/currents-and-insider) - [Cypress.io Blocking of Sorry Cypress and Currents](https://currents.dev/blog/v13-blocking) - [Case Study: Planable](https://currents.dev/blog/currents-and-planable) - [Cypress test replays with Cypress Debugger](https://currents.dev/blog/currents-cypress-replay-debugger) - [Case Study: Crunchbase](https://currents.dev/blog/currents-and-crunchbase) - [GitHub Actions Matrix Job URL for Parallel Cypress Tests](https://currents.dev/blog/github-actions-cypress-job-url) - [Currents has joined TinySeed](https://currents.dev/blog/currents-tinyseed) - [Cypress Dashboard vs Currents - Ultimate Comparison Guide](https://currents.dev/blog/currents-vs-cypress) - [Parallelizing Cypress with Jenkins, AWS, and Sorry Cypress](https://currents.dev/blog/parallelizing-jenkins-aws-sorry-cypress) - [Cypress parallelization tools comparison](https://currents.dev/blog/cypress-parallelization-tools) - [Currents is out of Beta](https://currents.dev/blog/currents-out-of-beta)