Our product currently integrates on top of existing test libraries (and we're starting with Cypress).
If you'd be referencing how Cypress compares with Playwright - I'd say the two largest differences is Cypress has a promise-like/chain based syntax for authoring tests versus Playwright allows for async/await syntax. Outside of that, Cypress provides a pretty awesome local developer experience (imo) whereas Playwright has a leg up in flexibility (multi-tab support, browser support, better simulated actions like mouse hovering).
If you're referencing how does our tool compare to what you might get with Playwright out of the box, Playwright does offer a really awesome trace viewer (https://playwright.dev/docs/trace-viewer) and actually had a brief chat with the original PM on Playwright a few weeks ago about it. It does capture a lot of similar debugging information - where we differ today from our debugger is a focus on making these historical runs easily accessible for engineers (don't need to go to your CI run, unzip an artifact, load it up locally, or build your own analytics dashboard for trends) as well as iterating on DX improvements like letting you scroll through/search all your network requests at once, and then jump to the point in time where a network request was made, which isn't possible in the trace viewer.
In the future we're looking into providing deeper information beyond just browser-level telemetry, so a few ideas we've kicked around with our users include capturing Redux/React state (like Redux or React dev tools do locally today), or even being able to sync up backend telemetry relative to what's happening in the browser. (Ex. show me the logs that were printed to stdout in the app server container when my test was clicking on the check out button).
If you'd be referencing how Cypress compares with Playwright - I'd say the two largest differences is Cypress has a promise-like/chain based syntax for authoring tests versus Playwright allows for async/await syntax. Outside of that, Cypress provides a pretty awesome local developer experience (imo) whereas Playwright has a leg up in flexibility (multi-tab support, browser support, better simulated actions like mouse hovering).
If you're referencing how does our tool compare to what you might get with Playwright out of the box, Playwright does offer a really awesome trace viewer (https://playwright.dev/docs/trace-viewer) and actually had a brief chat with the original PM on Playwright a few weeks ago about it. It does capture a lot of similar debugging information - where we differ today from our debugger is a focus on making these historical runs easily accessible for engineers (don't need to go to your CI run, unzip an artifact, load it up locally, or build your own analytics dashboard for trends) as well as iterating on DX improvements like letting you scroll through/search all your network requests at once, and then jump to the point in time where a network request was made, which isn't possible in the trace viewer.
In the future we're looking into providing deeper information beyond just browser-level telemetry, so a few ideas we've kicked around with our users include capturing Redux/React state (like Redux or React dev tools do locally today), or even being able to sync up backend telemetry relative to what's happening in the browser. (Ex. show me the logs that were printed to stdout in the app server container when my test was clicking on the check out button).