jasonlaster11

Cypress also blocked deploysentinel.com which introduced Session Replay for Cypress and Playwright tests last fall.

If Cypress users want to view a dashboard or session replay of their failed or flaky tests, they'll need to pay for Cypress Cloud which can easily be 6 figures.

I'm hopeful that after the dust settles, Cypress will clarify their stance on the ecosystem. It's clear that Playwright has the momentum, but Cypress can still be successful if they are able to innovate alongside their community and rationalize their pricing.

Unfortunately we don't support python yet, but if you ever encounter a similar heisenbug in JS, you can try recording it with Replay.io

Congrats on launching! Using Session Replay in the CI space makes a lot of sense. And agreed that there’s a lot that can be done by hooking into Cypress’s events. By the way, we’re doing the same and hope to show a Cypress reporter soon as well.

Re pricing: we’re still refining the pricing, but we assume that most of the time you’ll only want to debug the failing tests and while the recordings are fairly small, the larger piece is actually replaying the browser as it ran before so you can add print statements in your application and play to when a network request was returned or an error was thrown.

Suggested this to Greg a couple of months ago! We sometimes use Pernosco to record the Replay Chromium and Firefox. Would love to see how Undo does in comparison.

Likewise, if you're building more web apps, we'd love to hear how Replay.io works for you. We're on a shared journey to bring TTD to the world.

Absolutely. It's really nice to be able to simple record the replay and then share the replay with others. Because replays are just websites, anyone can view them in any browser.