Record by clicking
Click through your app in a real browser. Then save the recording or reject it. To save, type where it belongs, and the AI rewrites it into page objects.
Test management · Test runs · Automation
Your whole QA process
in one desktop app.
Write test cases, run regression and UAT rounds, and share the results. When a case is ready, let AI turn it into a Playwright test that runs against your real app. It checks every locator and keeps going until the test passes.
Version 0.1.0 · Windows 10 and 11
From the first test case to a green test run
-
1
Plan
Write test cases page by page, or describe a feature and let AI draft them for you.
-
2
Execute
Collect cases into a regression or UAT run, and go through them step by step.
-
3
Report
Check the pass rate and the chart for each page, then export the results to Excel, PDF or HTML.
-
4
Automate
Turn stable cases into Playwright tests with one click, and run them on any environment.
Test cases
Test cases your whole team can follow
Every case has preconditions and numbered steps, and each step has its own expected result. That makes it clear where something failed, not just that it did.
- Organise by page. Group cases into pages and subpages, such as Checkout › Payment, that match your product.
- Generate with AI. Describe how the feature works, its acceptance criteria, roles, data and what's out of scope. Pick Smoke, Standard or Thorough coverage, then keep the drafts you like.
- Edit freely. Add, insert, reorder and delete steps. Set priority, status and tags like smoke and regression. Drag cases between pages.
- No lock-in. Cases are saved as readable Markdown files in your project's Git repository.
Test runs
Regression and UAT rounds, tracked properly
Create folders for each release, regression cycle or UAT round. Inside them, create runs with exactly the cases you need, filtered by page, priority, smoke or regression.
- Step by step. Mark each step passed or failed and write down what actually happened. Then set the case result: passed, failed, blocked or skipped.
- Defects and comments. Add a defect ID and a note to any case, and see who ran it and when.
- Results at a glance. See the pass rate, progress and a chart for each page while the run is still going.
- Export and sign off. Export to Excel (CSV), PDF or HTML. Completing a run locks it until it's reopened.
Automation
Turn a test case into a test that actually works
Press Create automated test on any case. The preconditions become setup, and every step becomes a Playwright test.step with its own assertion. The test is linked back to its case.
- Locators are checked, not guessed. The AI opens your app in a browser, makes sure each locator matches exactly one element, and runs the new test until it passes.
- Clean code. Tests follow the Page Object Model and your team's rules, and existing page objects are reused instead of copied.
- You stay in control. Every check and run is shown as it happens. Nothing is saved until you apply the changes.
- Fix with AI. When a test fails later, the AI reproduces the failure, looks at the page as it is now, and fixes the page object. Or it tells you it found a real bug.
A complete Playwright workbench
Everything you need to build and maintain your automated suite, without leaving the app.
Run exactly what you need
Pick one test, a section, a file or everything. Failures show the error, screenshots, trace and video, with a one-click AI fix.
Code editor
Write tests by hand with a searchable file tree. Move files and folders by dragging them, and imports update for you.
Git built in
Commit, branch, fetch, pull and push much like in GitHub Desktop, and open pull requests on GitHub or Azure DevOps.
Environments
Switch between dev, staging, UAT and production, and the base URL follows. Production asks before anything runs there.
Visual tests
Screenshot comparisons sit next to your E2E tests. See the expected, actual and diff images side by side.
Browsers and settings
Choose which browsers run which suites, tags and pages. Edit retries, timeouts and traces in a form, or edit the config file directly.
Your team's rules
Write the conventions the AI must follow, or bring the rule files you already have, such as .cursor/rules.
Secrets stay secret
Edit .env in the app. Values are masked before anything is sent to the AI, and your API key is encrypted on your PC.
Questions
Do I have to use the automation features?
No. Test cases, test runs and reports work on their own, without any coding and without an AI key. Add automation whenever your team is ready.
What do I need to run QA Studio?
Windows 10 or 11, and Node.js 20 or newer, which QA Studio uses to set up and run Playwright in your projects. Git is recommended. The AI features need an Anthropic (Claude) or OpenAI API key.
Does my Claude Pro or ChatGPT Plus subscription work?
No. QA Studio uses the providers' APIs, which are billed separately from chat subscriptions. Create an API key in the Anthropic Console or on the OpenAI platform, and add it in Settings.
Can I use an existing Playwright project?
Yes. Open any Playwright project. QA Studio adds one small settings file and leaves your config, folders and Git history as they are.
Where is my data stored?
In your project folder, on your computer. Test cases are Markdown files, runs are JSON files, and tests are regular Playwright code. All of it can be versioned with Git and opened in VS Code, Cursor or any other editor. Nothing is uploaded except what you send to the AI provider you chose.
Windows warns me when I run the installer. Is that expected?
Yes, for now. The installer isn't code-signed yet, so Windows SmartScreen may show "Windows protected your PC". Choose More info, then Run anyway.