Replay for Test Suites helps teams record their Playwright and Cypress tests in CI and debug them after the fact with Browser DevTools, retroactive console logs, and our new testing panel.
Hello Product Hunt,
When we launched Replay DevTools two years ago, we were excited to share how Time Travel could help teams capture hard-to-reproduce bugs and inspect them later with Browser DevTools.
Over the past two years, teams have recorded countless bugs and open source projects like NextJS, Redux, and Apollo have started requesting replays with their bug reports.
Today we’re excited to take on the thorniest hard-to-repro bug out there: the flaky browser test.
Here are some of the features we’re most excited about
On the recording side
✅ Built in support for Cypress + Playwright
⏺️ GitHub Action and popular CI environment support
🏃 Incredibly fast recorder
On the debugging side
▶️ Play to any test step
⚛️ Jump from a test command into your React component
🛠️ Inspect your app with Browser DevTools
We love hearing from fellow builders. What do you love and hate about your end-to-end test suites?
As users, we spend a large percentage of our day in the browser. But as creators (engineers, product, design) we somewhat dread browser testing and unhelpful bug reports. Traversing the user timeline has always been the audacious goal. I've been watching the Replay team for more than a few years (also within the bowels of Firefox) now, and this latest release brings the era of time travel well upon us 🚀...
Well played @jasonlaster11
@david_sipos Great question. Replay lets you record and debug your test after the fact. It's like capturing that flaky test in a bottle and debugging it live with Chrome + Cypress DevTools.
@david_sipos feel free to email me at jason@replay.io if you have any questions. Also forgot to mention that Cypress Studio is great at what it does. I feel like the two are better together :)
Wow, congratulations on launching such an amazing tool on Product Hunt! 🎉 I am so excited to hear more about how Replay DevTools can help with flaky browser tests 🤔 Could you share some use cases or examples of how teams have successfully used Replay DevTools to enhance their testing process? And I have to say, the feature set you have listed is quite impressive! 🤩 I love the idea of being able to jump from a test command into a React component and inspect the app with Browser DevTools 🙌 It seems like Replay DevTools is the missing piece in the puzzle of end-to-end testing. Keep up the fantastic work and I can't wait to see what new features you'll add in the future! 💪
@gabriel_nori You're 100% right. React is the missing piece. Once you connect Cypress + React, you have a much better idea of how you're application is tested.
A user recently fixed a flaky test where sometimes a couple of milliseconds passed between calls and sometimes it didn't. It sounds simple, but being able to open two replays side-by-side where one passed and the other failed, and add console logs in both is kinda all you need.
Replay