Replay.io

Good news! You can debug both Playwright and Cypress tests with Replay: 🎭 -> https://lnkd.in/dkn5QmjX 🌲 -> https://lnkd.in/dFgZsaw2

Help us bring time travel to the world!

Replay is a "record & inspect" tool. Record your app or your e2e test execution with Replay Browser, and then inspect it with Replay DevTools. Then travel back in time. Pause at the perfect moment. Get an insight like never before.

Print statements are the most powerful feature of Replay. They allow you to take a look into application runtime. This enables you to debug your end-to-end tests or issues that occurred during a recording. We added a new lesson to our ⭐ Replay.io course ⭐ where you can learn all about print statements and how to use them Go watch and subscribe, because more are coming!

Navigation issues in React can be some of the trickiest problems to debug. In this quick video, you can learn how to get insight into all navigation changes https://buff.ly/3P2iAXE

Flakiness happens in the gaps between your test script commands. But you can get more insight with Replay DevTools that contain everything that’s contained within these gaps. You drive down the time spent debugging into a fraction, and fix test flakes once and for all https://buff.ly/4bYAt3i

Has your test script ever betrayed you? Mis-typing in an e2e test is one of the most annoying problems when running test automation. Specifically, because it is hard to tell why the problem even occurs. When you run your tests with Replay Browser, these problems become less mysterious. https://buff.ly/49QriQP

"Element not visible" - is this a problem in your test or in your app? Hard to say without some more context. You can run your test automation with Replay Browser which will provide you the much-needed insight. See how you can explore the source file from your CI test run.

Fixing a flaky test? Don’t run it on repeat, but fix it with confidence. https://replay.help/social

How would you debug a test failure that was caused by a 2 px difference? This was exactly the problem that the Metabase team was facing as we helped them drive down their test flakes. Recording the test runtime was essential for being able to find this issue. It involved digging into React component props and examining function calls. Read to learn more about the debugging process using Replay DevTools