01 · Plan
Test cases your whole team can follow
Every case has preconditions and numbered steps, and each step has its own expected result, so it's clear where something failed, not just that it did.
- Pages and subpages, such as Checkout › Payment
- Priority, status, smoke and regression tags
- Saved as Markdown in your Git repository
02 · Plan with AI
Describe a feature, get the test cases
Tell the AI 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.
- Uses only what you give it, and lists its assumptions
- You choose which cases to keep
03 · Execute
Regression and UAT rounds, step by step
Create folders for each release or UAT round and runs with exactly the cases you need. Mark each step passed or failed, and write down what actually happened.
- Passed, failed, blocked or skipped for every case
- Defect IDs, comments, who ran it and when
04 · Report
Results while you test, ready to share
See the pass rate, progress and a chart for each page as the run goes. Export to Excel, PDF or HTML, and complete the run to lock it until it's reopened.
- Failed and blocked cases with their defects
- Excel (CSV), PDF and HTML exports
05 · Automate
A test case becomes a test that actually works
Press Create automated test. Preconditions become setup and every step becomes a Playwright test.step. The AI opens your app, checks each locator matches exactly one element, and runs the test until it passes.
- Wrong guesses are caught before they reach your code
- Page Object Model and your team's rules
- Nothing is saved until you review the diff and apply it