
Design
Test cases from a requirement
Equivalence partitions, boundary values, decision tables and state transitions, drawn from the requirement, its mock-ups and your shared steps. The AI also flags what the requirement leaves ambiguous.
testons.net brings test plans, requirements, cases, test runs and defects into one tool, with ISTQB vocabulary. For teams testing web, mobile or desktop software.
No credit card · free, unlimited viewers
Sprint 14 — Bookings

The ISTQB test process, end to end
A requirement knows its cases, a case knows its results, a failure knows its defect. Scroll: every step has its screen.
Scope, approach, risks, entry and exit criteria. The plan gets approved, and its criteria are measured continuously across all its test runs.

The traceability matrix crosses requirements, cases and latest results. Uncovered requirements stand out.

Steps or Gherkin scenarios, shared steps, custom fields, risk-based priority. Every change to an approved case creates a new version.

One execution per case and configuration, assigned to the team. Exit criteria are re-evaluated with every result.

Progress, risk-weighted pass rate, workload per tester, defects by severity and day-by-day trends.






Built for the field
Execution mode fits in one hand: steps to tick, a thumb-sized verdict, a timer, screenshots pasted from the clipboard. On a computer, P, F, B and S are all you need.

AIAI assistance
Claude, by Anthropic, prepares the work at every step of the ISTQB test process. Nothing is written without review: every proposal arrives as a draft, marked AI, and stays traced in the audit log.

Design
Equivalence partitions, boundary values, decision tables and state transitions, drawn from the requirement, its mock-ups and your shared steps. The AI also flags what the requirement leaves ambiguous.

Execute
Title, reproduction steps, justified severity and the identical defect already open, from the steps, screenshots and logs. On a phone, a dictated note fills in the result.

Steer
Progress, exit criteria explained, risks and a release recommendation, reviewed and then carried into the PDF under your name.

Ask
“Which critical defects are open?” The AI queries the project with your permissions, no more, no less, and says where it looked.
And everything else
One include in .gitlab-ci.yml: every pipeline uploads its JUnit reports and creates an automated test run linked to your cases.
RES-R3 · pipeline #2986442580 · main · 217 tests
A defect becomes a GitLab, GitHub, Jira or Linear issue. Status and severity follow both ways.
Wave, Orange Money, Free Money or card. Prices in CFA francs in the WAEMU zone, in euros elsewhere.
Import your repository with a row-by-row error report, export the results of every test run.
Test Progress and Test Completion Reports in one click, lessons learned included.
Interface, emails and notifications in each member's language.
For every team that answers to its customers, and to its auditors.
Each organization is isolated at the database level.
TOTP and passkeys, enforceable for the whole team.
Who did what, when and from where — append-only and exportable.
Each customer decides who does what, down to the project.
Every attachment is scanned before being served.
Approved plans and frozen versions: an executed test run never changes.
14 days of the Business plan for the whole team, then the free plan if you don't subscribe.
Try it free for 14 days