Test case creation
The test plan written before testing starts: what will be tested, on which platform with which assistive technology, and what counts as a pass.
What goes into a test set
-
Scope, agreed in writing
The pages, flows and states in the set, and the ones left out of it. What is out of scope is written down as plainly as what is in.
-
Screens and states
Every screen with the states that break in practice: empty, loading, error, validation, success, and the timeouts between them.
-
Platform and technology pairs
Which cases run in which browser, on which device, with which screen reader, at which text size, keyboard only or by voice.
-
Pass conditions
What a passing result looks like for each case, so a fix can be confirmed and a retest cannot be argued about later.
How we write them
From your product outwards, not from a checklist inwards.
Walk the product with you
A session through the flows that matter, so the set covers how people actually use it rather than every screen equally.
Write one case per risk
Each case states the starting point, the steps, the platform it runs on and what should happen. Cases that cannot fail are cut.
Map the coverage
Every case is tied to the success criterion it proves, and the map shows the criteria the set does not reach.
Hand it over and hold it
The set is yours to run. We run the first pass with your testers and keep it current as the product changes.
Test case questions
Do we need test cases before an audit?
No. An audit finds the barriers that are in the product as built. A written set pays off when the same product will be tested more than once: a release cycle, a second platform, or a buyer who wants evidence of what was covered.
Who writes the test cases?
We write them with your team, because your product knowledge is what makes a case specific. You keep the set and can run it again without us.
What do we receive?
A test set naming each case, the platform and assistive technology it runs on, the criterion it proves and what a pass looks like. Plus a coverage map showing what the set does not cover.
Then audit or test the build · Or recheck after each release
Book your free call
Show us your product in 30 minutes. We tell you whether a test set is worth writing for it.