Show HN: Playwright Test Studio | Hacker News Reader

Show HN: Playwright Test Studio

github.com

4 pointsbaudehlo6 comments

PTS is an app I wrote to enable you to write playwright tests in English, and manage your test suite in a UI.

It's crafted after the postman/bruno style of collections of tests with variable interpolation.

I wrote this because I couldn't find anything similar to a previous YC product I'd used called Rainforest.

It runs your tests and takes screenshots along the way, so you can see where it went wrong. Run multiple browsers for the same test too.

It's MIT, and I'm open to ideas or enhancements.

Open articleView on HN

This looks pretty cool, would love to try it.

One thing I'm trying to understand from the docs. I have 100s of playwright based BDD tests in my projects, especially the ones that are purely AI written. How does this interface with my existing tests? Does it scan the repo or is it meant to have it's own stand alone folder?

It doesn't interact with your code at all (yet). The tests are in English, so mostly it's not designed for developers.

It's an interesting idea, but currently other apps are way better setup to scan code (like vscode and claude code). What I have done is ask claude to scan the codebase and generate a full series of English language tests in a markdown file. Would be good to ingest that, but for now I'm just using cut and paste.

Very cool, I think one of the biggest opportunities Playwright has is making it a more general purpose tool for non-developers, writing the tests and getting them to a state where they reliably pass has always been so much more finicky than it should be.

That's the idea, it's very much for non-developers.

I really like this space. I prototyped a concept last year for product/qa teams to write the tests, I was able to run Playwright in a docker container and stream the session to the browser using VNC and web sockets to extract the test recorder and relay commands, allowing the user to run Playwright and record tests without needing anything installed.

It was a lot of fun, but what turned me off it was the likelihood anyone not already using Playwright would have to update their frontend and keep streamlining that before they really got any value out of it.

https://imgur.com/a/4UzOwJ8

Yeah my big thing was this needed to be local, because I want to test against localhost, so rather than a web app, a desktop app made sense. I'd like to build in some sort of team features to it, so that you can collaborate with other people.

This was only my second desktop app ever, my first being a DVD burning app for the Mac, so you can guess how long ago that was!

Reply on news.ycombinator.com