A genuine Req2QA run — not a mockup. Requirements in, validated test coverage out, real live-execution results.
The requirements below come from a sample Incident Management requirements document written for this demonstration — the kind of document a client would supply.
1.2 The system must auto-generate a unique Incident Number (format INC#######) when a new incident record is created.
1.4 The “Caller” field must … allow free-text entry that creates a new caller record automatically if no match exists.
1.8 The “Channel” field … must default to a sensible value when the incident is created through the standard form.
Req2QA generated 11 test cases from the requirements document and executed them unattended in a real browser. We show the three we have independently checked against their screenshots — including two where the software did not meet its requirement. The remaining results from this run are still under review, and we don’t publish a result until it has been checked.
| ID | Test case | Req. | Result |
|---|---|---|---|
| TC-003 | Create two incidents and confirm each receives a different Incident Number | 1.2 | PASS |
| TC-014 | Channel field has a sensible default on a new incident | 1.8 | FAIL |
| TC-007 | Free-text Caller that doesn’t exist is auto-created | 1.4 | FAIL |
Both FAILs are gaps between this sample requirements document and how the developer instance is configured — the instance doesn’t do what the document asks. They are not defects in ServiceNow itself; they show Req2QA reporting a mismatch rather than assuming a PASS.
Executed 24 September 2026 (Australian time) against a live ServiceNow developer instance. Times inside the screenshots are shown in the instance’s own time zone.
Cropped to the evidence; click any screenshot to view it full size.
TC-003 — PASS. Both test incidents appear in the list with different numbers, INC0010009 and INC0010010.
TC-014 — FAIL. A brand-new incident opens with Channel set to “–– None ––”. Requirement 1.8 asks for a sensible default — this instance doesn’t provide one.
TC-007 — FAIL. Typing a caller who doesn’t exist is rejected with “Invalid reference”; no record is offered or created. Requirement 1.4 expects the new caller to be created automatically.
R1. The system shall allow an HR administrator to add a new employee record by providing first name, middle name (optional), and last name.
R3. The system shall allow an HR administrator to optionally attach a profile photo (JPG, PNG, or GIF, up to 1MB).
Typical engagements run 25–300 test cases; this is a genuine excerpt, not a curated best case.
| ID | Test case | Type | Result |
|---|---|---|---|
| TC-001 | Add new employee with first, middle, and last name | Happy path | PASS |
| TC-003 | Attempt to add employee without a last name | Negative / validation | PASS |
| TC-007 | Attach a valid JPG profile photo within the 1MB limit | Edge case | PASS |
3 test cases executed, 3 passed, 0 failed, 0 blocked. Executed 2026-09-21.
Click any screenshot to view it full size.
TC-001 — record created and saved successfully.
TC-003 — form correctly blocked save with a "Required" validation message.
TC-007 — the attached test photo is intentionally watermarked "generated by Req2QA — not a real document." We never use realistic-looking fake photos of real people as test data — see our Security Overview for how we handle test data generally.
