Customer Success Story: Sherpany

Introduction

As Sherpany's Playwright end-to-end test coverage grew rapidly, the QA team began facing recurring challenges around test suite performance and reliability. More tests meant longer PR cycles and more time spent chasing failures, without a clear picture of what was flaky, what was broken, and what was worth fixing. Sherpany needed the kind of centralized reporting and flakiness analytics QA teams get from the Cypress Dashboard, but built for Playwright. That search led them to Currents.

Company Overview

Sherpany is a meeting management software for boards and executive teams. It centralizes agendas, documents, decisions, and actions into one secure environment, helping boards and leaders optimize the full meeting lifecycle. Sherpany enables boards and executive teams to make well-informed decisions, maintain strong governance, and ensure follow-through and accountability.

Key Challenges

Before adopting Currents, Sherpany had no dedicated test reporting platform. The team relied on reports that Playwright produces natively and logs from their CI runner. That setup worked when the E2E project was smaller, but as coverage expanded, recurring challenges surfaced around performance and reliability.

The team observed:

• Longer PR cycle times despite having more areas covered by tests.
• Reduced change confidence as failures became harder to interpret at scale.
• Manual flakiness investigation that consumed QA time without delivering a full picture of suite health.

At the beginning of our Playwright E2E project, native reports and runner logs were sufficient. But rapid growth of test coverage surfaced recurring challenges related to performance and reliability. We observed increased PR cycle time and reduced change confidence, despite having more areas covered with tests.

Sherpany QA Team

Test flakiness was a major challenge for the QA team. Because the product evolves quickly, they needed an equally fast feedback loop to stay confident that quality remained high and that the test suite stayed reliable and valuable.

One of the main struggles of our QA team was to keep control over test flakiness. Before Currents, we used to spend time investigating flakiness and related metrics manually, which was time consuming and still didn't give us the full picture.

Sherpany QA Team

Why Sherpany Chose Currents

Sherpany discovered Currents while searching for a Cypress Dashboard equivalent built for Playwright. After evaluating the platform, the team confirmed it could meet their core needs: building and maintaining a reliable, scalable test suite.

Decision factors included:

• Live test run monitoring for faster feedback during CI.
• Reporting and failure analytics to replace manual log review.
• Flakiness and failure-rate tracking with clear signals on what to fix next.
• Competitive pricing and a collaborative, responsive support team.

Currents helped Sherpany reduce suite flakiness from roughly 5% of test count to near zero (0.1–0.2%), with clear visibility into whether remaining issues belonged on the Playwright side or reflected real product improvement areas.

Implementation

Adopting Currents was straightforward, with the initial setup requiring minimal effort on Sherpany’s side.

Implementation was extremely easy. We passed credentials and Currents started delivering its value right away. We didn't have anything to be migrated. The only challenge was on our side to find the best strategy of setup and test runs.

Sherpany QA Team

Use Cases & Results

Currents became central to how Sherpany monitors product stability and test suite reliability. The team tracks flakiness rate per run, observes trends in failing or flaky tests, and triages fix priority accordingly. Currents Actions also help unblock development when failures turn out to be false alarms.

Key outcomes included:

• Flakiness reduced from ~5% to 0.1–0.2% of tests, with peak flaky occurrences dropping from ~40 down to 0–2.
• Suite runtime improved by ~39% for ~900 test cases, from ~18 minutes to ~11 minutes, driven by stability improvements and optimizations informed by duration metrics.
• Faster triage by identifying trends in failing and flaky tests and prioritizing fixes accordingly.
• Unblocked development using Currents Actions when failures were not product defects.

Currents gave us the tools to lay a solid foundation for a fast, reliable end-to-end test suite.

Sherpany QA Team

Product Evaluation & Customer Experience

Sherpany evaluates Currents as stable and reliable. So far, the team has not experienced platform or runner issues related to downtime.

On support and customer relationship, the experience has been consistently positive:

We really appreciate our relationship with Currents. The team is very supportive and proactive.

Sherpany QA Team

Impact of Currents

The most important impact for Sherpany's QA leadership is time reclaimed from debugging and investigation.

Hours saved by the team weekly on debugging and investigation is the main and most important impact for me as a team leader. We can use this time to focus on what matters most and keep the quality standard of our project high.

Sherpany QA Team

Conclusion

By adopting Currents, Sherpany transformed its fast-growing Playwright suite from a source of uncertainty into a reliable quality signal. Flakiness dropped to near zero, while test runtime decreased by nearly 40%. With greater visibility into test results, the QA team could prioritize fixes more effectively and unblock development with confidence. Currents gave Sherpany the foundation to scale end-to-end testing while improving the speed and reliability of its CI pipeline.

---