Case Study: Hover
Trademarks and logos mentioned in this text belong to their respective owners.
How Hover cut testing costs and improved developer experience and efficiency with Currents.dev.
Introduction
Hover Inc is helping construction professionals easily and accurately measure, scope and estimate projects. It also helps professionals and homeowners collaborate by providing easy-to-use and powerful design tools.
In this article, we show how Hover improved their front-end testing by adopting Currents and later switching from Cypress to Playwright. What started as a search for a simpler, more cost-effective test dashboard turned into a smooth transition toward a more powerful testing setup.
Challenge
Before Currents, Hover was using Cypress.io to manage their UI test suite. While Cypress served their basic testing needs, it offered more than they needed at a cost that felt unjustifiable. Additionally, growing concerns around Cypress blocking third-party integrations further pushed Hover to explore alternatives.
Thomas Genin, Director of Engineering at HoverWe weren’t doing anything complex. Our developers just needed to see the failures. Paying that much made no sense.
Solution
Hover discovered Currents.dev through the startup accelerator TinySeed, which emphasized Currents' cost-effective, Cypress-compatible dashboard. The team ran a limited proof of concept, quickly validated the platform's capabilities, and transitioned fully within weeks.
Key factors in adoption:
- Seamless integration with existing test infrastructure.
- Migration required only 2-3 lines of config changes.
- Immediate support for Playwright alongside Cypress.
- Smooth UI with videos, stack traces, and test histories.
Implementation & Migration
From Cypress to Currents:
The initial migration was fast and painless. Currents has the key features — screenshots, video playback, stack traces — without needing major changes or custom tooling.
From Cypress to Playwright:
Hover began a gradual migration to Playwright after Currents added its support. While the Playwright migration required more effort (codebase updates, test auditing), the Currents platform continued to support both test frameworks seamlessly.
Thomas Genin, Director of Engineering at HoverWe made an executive decision: all new tests in Playwright. Currents supported both, so we didn't have to think twice.
Use Cases
Main Use Case: Diagnosing failing tests quickly via Currents' dashboard (recordings, logs, and flake analysis)
Hover runs two types of test suites:
- PR-level tests on each contribution.
- Production-level tests every 15 minutes for live monitoring.
Currents' flakiness data helps Hover track outages and test reliability over time.
Thomas Genin, Director of Engineering at HoverPeople use it. You see Currents links in Slack messages among the team all the time. It speeds up diagnostics and cuts the need to run things locally.
Results
- Significant cost savings (~80% reduction compared to Cypress)
- Minimal migration effort (days, not weeks)
- Improved developer velocity through better failure visibility and diagnostics
- Increased team adoption — evidenced by widespread Currents link sharing and Slack integration
- Exceptional technical support during adoption of the Currents Dashboard and migration to Playwright highlighted Currents' commitment to efficiency.
Thomas Genin, Director of Engineering at HoverCurrents helps us accelerate bug resolution in both development and production environments.
Looking Ahead
Hover is exploring Currents’ test orchestration features to distribute test execution across multiple runners. While initial setup appears complex, they appreciate the platform’s flexibility and Currents’ offer to assist with implementation.
Thomas Genin, Director of Engineering at HoverCurrents just works. Nobody complains, and that’s the best kind of tool.
Conclusion
To sum up, Currents has become a reliable part of Hover’s testing and release process, helping the team catch issues early and resolve them faster.
Thomas Genin, Director of Engineering at HoverCurrents helps us quickly diagnose issues in our end-to-end tests and speeds up fixing problems across both development and production.
Join hundreds of teams using Currents.
