Customer Success Story: Juvare
How Juvare restored test reporting visibility during their Cypress-to-Playwright migration with Currents.

Introduction
As Juvare began migrating its end-to-end test suites from Cypress to Playwright, the team quickly realized that something critical was missing: centralized test reporting. While Playwright better fit their diverse and evolving technology stack, the move meant losing the dashboards and failure analytics they relied on for troubleshooting and tracking stability over time. Juvare needed a lightweight and reliable way to restore insight into test health. That search led them to choose Currents.
Company Overview
Juvare builds critical incident management and public safety software used by governments, healthcare systems, and large organizations worldwide. With a wide variety of products and technology stacks, maintaining visibility into testing and reporting was essential as they migrated from Cypress to Playwright.
The Decision to Migrate to Playwright
When evaluating their testing strategy, Juvare's team realized they needed a testing framework that could handle their diverse technology stack.
At the time we chose Cypress, it was the most modern tool available, but it had limitations. We needed a tool that could cover both our established products and newly developed ones. Playwright fit our needs better, which is why we decided to migrate.
Key Challenges
Before adopting Currents, Juvare faced several testing challenges:
- Loss of reporting and troubleshooting: Migrating to Playwright meant losing the cloud-based dashboards and history they relied on for flake trends, failure investigation, and test stability over time.
- Need for lightweight, easy-to-use insights: The team needed a solution that would quickly surface meaningful stability signals (failures, reruns, and duration trends) without adding operational overhead.
- Maintaining consistency across many projects: With 20+ active development projects, keeping track of test stability and performance without centralized reporting was difficult.
- Alternative solutions were costly: Internal tools or other platforms required significant setup and maintenance effort, which was impractical.
We were looking for a lightweight solution, easy to use, which would give us the same benefits, or even more, than we had with Cypress.
Implementation
Adopting Currents was straightforward. Teams followed simple documentation and set it up independently.
All of the teams managed to set it up on their own. We prepared five bullet point guidelines from the documentation, and that was it. There was no complicated setup. Teams enabled it and it worked as expected.
Currents integrated directly with their Playwright test suites, providing centralized dashboards for monitoring test execution and troubleshooting.
Use Cases & Results
Currents became a central part of Juvare's testing workflow, restoring the visibility they had lost when leaving Cypress. Instead of waiting for a full suite to finish before starting triage, Currents provides live results as runs progress. This feature stood out immediately, generating excitement across teams:
The team was fascinated when they started to use Currents. They were getting real-time results, and our international communication channel was flooded with excitement.
Key ways Juvare leveraged Currents included:
- Tracking test suite metrics: Teams could monitor flake trends, run duration, and failure patterns as runs progressed and over time.
- Troubleshooting made simple: Currents helped developers identify and address issues sooner, rather than waiting for end-of-run summaries.
- Controlling test execution: Features like quarantining known flaky tests and using tags to scope runs gave teams controlled flexibility during complex deployments and the Playwright migration.
- Project oversight: Managers could now identify which projects were more stable and allocate resources where needed.
Most of our suites are more stable than we thought. Currents gave us numbers to talk about with engineering leadership and helped us identify where to assign resources.
Product Evaluation & Customer Experience
Juvare praised Currents for its stability, continuous product evolution, and strong customer relationship:
- Reliability: The platform has been stable and has worked as expected.
- Product evolution: The product is actively evolving, with updates driven by customer needs.
- Customer relationship: Feedback loops are fast, and requests are handled with minimal friction.
From a customer relationship perspective, I love what we have. The feedback and response is really quick. I couldn't want more.
Impact of Currents
Currents restored the visibility Juvare had lost, empowering teams to manage multiple projects confidently:
Without Currents, we'd lose centralized visibility into test quality across projects. With over 20 projects in Currents, that reporting helps us track implementation quality, prioritize improvements, and deliver better solutions for our clients.
Conclusion
By adopting Currents, Juvare regained critical visibility during their Playwright migration, ensured live insights into test performance, and empowered teams to share actionable metrics with engineering and leadership. Currents became an essential part of their workflow, maintaining stability and confidence across multiple products.
Join hundreds of teams using Currents.
Trademarks and logos mentioned in this text belong to their respective owners.


