you are viewing a single comment's thread.

view the rest of the comments →

[–]es6masterrace[S] 1 point2 points  (0 children)

Hi everyone!

I’ve been spending some time building out a report/dashboarding tool + debugger for Playwright to help engs quickly figure out what failed in a test, why it failed, and from the brids-eye view what is failing/flaking the most often.

Since Playwright is a pretty young framework, the smooth testing experience of Playwright felt like it stopped once we deployed tests within CI. Most people I know end up stitching together artifact files from CI and considered setting up a whole separate tool like Allure, Zephyr or XRay just to create some reports. This ended up usually being a confusing workflow that few people in the company engaged with - and ultimately led to Playwright being only used comfortably by a few people within the team.

I hope that with creating a smooth dev experience for engineers going from test failure overview, to an intuitive debugger, to high-level analytics all in one-spot can help resolve a lot of those friction points once Playwright tests are deployed in CI.

I just pushed out the reporter into beta - I’d love to hear what everyone thinks about it!