Browser-only checker
Test Case Quality Checker
Paste plain-language test steps and an expected result. The checker flags vague actions, combined steps, missing test data and results no one can verify — with a suggested rewrite for each finding.
- Fixed rules, no AI guesswork
- Your text stays in the tab
- Markdown export
Findings
Rule-based review
Paste your steps and select Check steps. Findings appear here, one rule at a time.
What it flags
Six checks on the words, not the app
Every finding points at a specific line and says what to write instead. The rules are deterministic: the same test case gets the same review.
- 01
Vague actions
“Click the button” and “check it” do not name a control or a visible outcome. The suggestion asks for the label and location.
- 02
Combined steps
Two actions in one line make a failure ambiguous. The checker asks you to split them so the failed action is obvious.
- 03
Unspecified test data
“A valid email” is a description, not a value. Another tester cannot reproduce the run without the exact input or a named fixture.
- 04
Missing expected result
Without a pass condition there is no test, only a list of actions. The checker reports the gap before you run anything.
- 05
Unobservable results
“It works” and “the page is correct” give a tester nothing to compare. The rewrite suggests text, a URL, a count or a status.
- 06
Test-level gaps
No starting point, duplicated steps and one-step “flows” are flagged at the test level, where a step-by-step review would miss them.
How to use it
- 01 Paste the steps, one per line.
- 02 Add the expected result — the visible change that means pass.
- 03 Run the check, fix what matters, then copy or download the report.
Example
Before and after a clarity pass
The steps below are pasted into the checker as-is. The rewrite keeps the same flow and adds the details a manual tester needs.
Open the checkout page.
Click the button.
Fill in the form with valid data.
Click Pay and wait for the confirmation.Expected result: “It works.”
Open https://shop.example.com/checkout.
Click the “Place order” button.
Enter 4242 4242 4242 4242 in the Card number field.
Click “Place order”.Expected result: the page titled “Order confirmed” shows an order number that starts with ORD-.
What it cannot do
- It does not run the test or touch your application. It only reads the text you paste.
- It cannot tell whether the steps cover the right behavior. Coverage is a human decision.
- The rules are heuristics written for English steps. A deliberately terse step can still be clear to your own team.
- It does not judge business rules, data correctness or whether an assertion is the right one.
Questions
About the checker
Does this checker use AI?
No. It applies a fixed set of text rules in your browser. The same steps produce the same findings every time.
What counts as a clear test step?
One action, a named target, and any value the tester must use. Put the pass condition in the expected result, not inside a step.
Is my test case uploaded anywhere?
No. The steps and expected result stay in this tab. Nothing is uploaded, stored or sent to a server.
Does it replace a test management tool?
No. It is a pre-flight clarity check on the words you already wrote. It does not run tests, verify coverage or connect to your application.
Ready to run the steps you just cleaned up?
BuniOD turns plain-language steps and an expected result into a reviewable browser scenario. Nothing runs until you approve it.
Free plan · 500K tokens/month · No card required