AI Artefact Review
Paste your own test case, test plan, bug report or test strategy. An AI mentor reviews it the way an experienced NZ QA lead would — pointing out coverage gaps, missing edge and negative cases, weak risk prioritisation, and anything that would slow a developer down. This critiques your work, not a fixed exercise.
How to get the most out of it
Most practice tools hand you a fixed scenario and grade a fixed answer. This one does the opposite: it reads whatever you wrote at work or in study and gives you targeted feedback you can act on today.
- Choose the artefact type so the mentor applies the right standard (a bug report is judged differently from a test plan).
- Paste your artefact into the box — or load one of the worked examples and edit it.
- Get mentor feedback — you receive a sectioned review covering coverage, missing cases, risk, clarity, ISTQB best practice, and the top three fixes to make first.
Remove any real customer or production data before pasting. Use synthetic values — the feedback is just as useful and you stay on the right side of the Privacy Act 2020.
How the mentor grades
Whatever artefact type you pick, the mentor structures its review around the same six headings, adapting the standard it applies to the artefact. It is told to act as an experienced New Zealand QA lead coaching a teammate — direct, specific, and focused on what to change next.
| Section | What the mentor looks for |
|---|---|
| Coverage | Whether the artefact covers the obvious paths and the realistic conditions a user would hit — not just the happy path. |
| Missing cases | Edge values, boundaries, negative and error paths, and combinations that are absent but matter. |
| Risk & priority | Whether effort is aimed at the highest-risk areas, and what a risk-based tester would test first. |
| Clarity & reproducibility | Whether someone else could follow the steps and reach the same result — unambiguous steps, clear expected results, and (for bugs) reproducibility. |
| ISTQB best practice | Alignment with ISTQB Foundation-level practice for the artefact type — test design techniques, traceability, and the expected fields. |
| Top 3 fixes | The three highest-value changes to make first, in priority order, so you know exactly where to start. |