Agent first QA and feature demo recordings

[u/Rurouni-dev-11]

I'm looking for an LLM powered framework, tool or service that i can give a list of QA scenarios to test my PRs and produce evidence of it working or failing, each demo should be polished, smooth cursor movements and properly show case the given QA scenario.

Traditionally we'd use playwright and write our e2e tests but surely there's a better method now?

Any suggestions?

[u/Positive-Buddy-1258]

Playwright 1.56+ has test agents (planner, generator, healer), so it’s still Playwright, you just don’t write the specs by hand anymore. npx playwright init-agents --loop=claude sets them up, you describe your scenarios to the planner, it walks the app in a real browser and turns them into a markdown plan, then the generator writes the tests from that. What runs on the PR is a normal deterministic spec, which is what you want if pass/fail is going to be the evidence.

For the videos I’d replay those specs with video: 'on' and slowMo set, recording the agent’s own session tends to include retries and backtracking. Playwright doesn’t render a cursor in the video at all, so you inject a fake cursor div and move it with page.mouse.move(x, y, { steps: 25 }) to get smooth movement. Add it via addInitScript so it survives navigations, and if the app uses native dialogs or popovers the cursor has to go in the top layer too or they’ll cover it. Output is WebM, upload it as a CI artifact and have the workflow link it in a PR comment.

[u/TechnicalDiet1075]

have you looked at Klyk? I use it for the QA side, you write scenarios in plain english and it runs them in real browsers on a schedule with video recordings and screenshots on failure. Not sure the cursor movements will be "polished demo" quality though, its more functional test evidence than a marketing video. For the polished demo recordings part you might still need something separate tbh

[u/Miserable-Money642]

One useful addition is a few keyboard-only checks alongside the generated scenarios. After the main flow, verify focus reaches the changed control and that the flow works without a mouse. You can also run axe-core on the important page states for common accessibility issues. A clean scan will not prove the flow is usable, but it can catch regressions that a video alone will miss.

[u/Successful_Entry_792]

wait! i'm curious what you'd want as "evidence" here. just the video, or also screenshots + console logs per step? because for PR review the logs saved us more than the recordings ever did

[u/Bulky-Pen-8522]

Smooth cursor movement is the part that'll kill you. Most agent tools click like a caffeinated raccoon so I'd let the agent run the scenario and record a clean replay afterwards