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.

I was curious how the game was built so I recorded this replay. Fun to see how it's using Supabase for the global state.

https://app.replay.io/recording/replay-of-youareatlascom--75...

Here ya go https://www.producthunt.com/posts/replay-for-test-suites

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.

Here's a replay of the rocket demo if others are curious how it works.

https://app.replay.io/recording/3cc35235-0a00-4fff-a1eb-7ffa...

https://www.loom.com/share/059d3d0770db447a8287c05bf269b476

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.

haha i didnt know about the advertising annecdote, but yeah we get a lot of references to Chronon from those that remember :)

We knew early on that a cool debugger wasn't going to cut it. Replay had to be super easy to adopt, fast, secure, and stable. That's our goal!

Apologies for that. That was what was easiest. How would you like to sign up?

Cypress support is coming soon. We've got playwright and puppeteer and have done the hard things with cypress. just have to get the dx polished.

https://github.com/RecordReplay/devtools/issues/3225

We've come a long way from the web replay days. We re-wrote the recorder to support additional runtimes like Node.js and Chrome. Replay is also cloud-based, so recordings are shareable and super fast.

We're really grateful for the support we had within Mozilla in the early days, but what we've come to learn is that projects like Replay really benefit from being able to be nimble and solely focused on a great experience which is difficult when you're a small feature in a larger product.

Also you can find our runtime forks and entire frontend on github. http://github.com/RecordReplay/

Happy to answer any additional questions.

We've come a long way from the web replay days. We re-wrote the recorder to support additional runtimes like Node.js and Chrome. Replay is also cloud-based, so recordings are shareable and super fast.

We're really grateful for the support we had within Mozilla in the early days, but what we've come to learn is that projects like Replay really benefit from being able to be nimble and solely focused on a great experience which is difficult when you're a small feature in a larger product.

Also you can find our runtime forks and entire frontend on github. http://github.com/RecordReplay/

Happy to answer any additional questions.

Session Replay records the DOM so it can be replayed like a video. Replay.io records the browser input so the browser session can be replayed again.

The biggest difference is that when you're viewing a replay, we're re-running the identical browser on our backend. This way you can debug the real thing.

The button is platform specific. So if you're on linux, it should show the linux icon. Windows support is on the way. It just entered alpha two weeks ago and we're targeting Beta early october. We record low level windows os calls and replay them on linux in a virtualized environment. Frankly thrilled it works at all :)

Thanks! Bret Victor has been my inspiration. Ever since I watch inventing on principle ten years ago, I knew this was what I wanted to build. In fact many folks on the team have a similar story. That's the crazy part about IoP for me. It's created a movement!

Replay has native support for React DevTools so you can easily inspect the component tree, props, state, etc... High level, because Replay replays the browser session everything just works. Even I can understand Angular apps and i've never built one ;)

Long story short, we forked the major browsers so that when you record we can capture the browser input (OS Library calls).

Brian walks through our approach here https://medium.com/replay-io/how-replay-works-5c9c29580c58

Yep! Tons on the site. Here's a Replay with an algolia search bug. Try adding a print statement in Hits.js!

https://app.replay.io/recording/cf2da81f-3a74-45ba-9241-f6d4...

Co-founder here. It feels incredible to be sharing Replay with all of you. It's been a labor of love the past five years!

Replay started off as a simple experiment in what would happen if we added a step back button and rewind button to the Debugger. We quickly realized two things. First, nobody uses breakpoints. Second, being able to share is so much more powerful than being able to rewind.

Here’s how Replay works today. Somebody on the team records a bug with the Replay Browser and shares the replay url with the team. From there, developers jump in and add print statements. The logs appear in the Console immediately so you don’t need to refresh and reproduce a thing.

Over the past year we’ve talked to hundreds of users, recorded 2.5 million replays, and worked incredibly hard to ensure Replay would be fast, secure, and robust from the get go.

Want to check it out? You can download Replay today. Can’t wait to hear what you think!

Interested in learning more, here is our announcement blog post https://medium.com/replay-io/launching-replay-the-time-trave...

Hey HN! co-founder here. It feels incredible to be sharing Replay with all of you. It's been a labor of love the past five years!

Replay started off as a simple experiment in what would happen if we added a step back button and rewind button to the Debugger. We quickly realized two things. First, nobody uses breakpoints. Second, being able to share is so much more powerful than being able to rewind.

Here’s how Replay works today. Somebody on the team records a bug with the Replay Browser and shares the replay url with the team. From there, developers jump in and add print statements. The logs appear in the Console immediately so you don’t need to refresh and reproduce a thing.

Over the past year we’ve talked to hundreds of users, recorded 2.5 million replays, and worked incredibly hard to ensure Replay would be fast, secure, and robust from the get go.

Another way to get involved is to join webreplay's slack

https://webreplay.slack.com/join

Web Replay spun out of Firefox [1] with the goal of helping product teams quickly reproduce and share bugs.

We think the current workflow of identifying minimally reproducible bugs and STRs leaves a lot of room for improvement. A better workflow would be to record a bug and share the recording with others. When developers can replay the recording with perfect fidelity, they can identify the root cause in CSS, JS, XHR or any other location.

Web Replay will be available for download (on mac osx) soon and early alpha feedback. If you're interested in being an early adopter, signup for the newsletter here https://webreplay.io/contact.html.

[1] https://developer.mozilla.org/en-US/docs/Mozilla/Projects/We...

Firefox engineer here. Happy to discuss any questions others might have.

I've personally been using watchpoints for the past 3 months and it has helped uncover some really difficult to find issues.

Very cool. The product looks great!

The plan is to do user testing on mac and if it is validated roll it out.

Replay requires a ton of difficult platform-level investment to get right and we're still actively finding bugs in the real world.

After it is validated, it will be easier to add the appropriate platform level bindings in other OSs.

Good question.

Everything is in firefox and open source

Here are the bugs: https://bugzilla.mozilla.org/buglist.cgi?cmdtype=runnamed&na...

Here's the primary directory: https://searchfox.org/mozilla-central/source/toolkit/recordr...

The debugger API is implemented in JS here https://searchfox.org/mozilla-central/source/devtools/server...

From a user perspective, we are trying to focus less on rewind and step back and more on adding logging retroactively.

The best way to think about this is when the user adds a logpoint, they'll immediately see the logs in the console.

We hope that making logging much better is a great way to help people better understand the recording.

Thanks for sharing!

Thanks for the feedback!

Replay is in the user-research and validation phase and still quite experimental.

firefox-replay.com is a work in progress. We're still sorting out the best way to communicate record and replay debugging and the new use cases.

We'll share more on @firefoxDevTools when we have something to report.