Built for QA engineers and test leads

Review requirements like a senior QA architect — in seconds

Upload a BRD, PRD, SRS, user story or functional spec. Get ambiguities and missing acceptance criteria flagged with reasons, a testability score per requirement, SMART / INVEST rewrites, and ready-to-run test case skeletons you can export.

Upload document See a sample finding

Ambiguity

Vague wording flagged with the exact phrase at fault.

Missing criteria

Acceptance criteria and edge cases that were never stated.

Testability score

0–100 readiness score per requirement.

Security

Auth, data handling and abuse-path gaps.

Accessibility

Keyboard, contrast and assistive-tech omissions.

Test skeletons

Positive, negative and boundary cases per requirement.

A real finding, end to end

Every flag shows why it was raised, so you can defend it in a requirements review.

Original requirement

The system should allow users to log in quickly and securely, and handle a reasonable number of concurrent users.

Findings

AmbiguityCritical
"Quickly" and "reasonable number" have no measurable threshold.
Why flagged: The words "quickly" and "a reasonable number of concurrent users" are subjective, so two testers would write different pass/fail criteria for the same requirement.
Missing Acceptance CriteriaMajor
No acceptance criteria define a successful or failed login attempt.
Why flagged: The requirement never states expected behaviour for wrong credentials, locked accounts or expired sessions, so negative paths cannot be verified.
SecurityCritical
No rate limiting, lockout or credential-handling rules are specified.
Why flagged: "Securely" is asserted but no control is named — brute-force protection, password storage and session expiry are all untested.

Suggested rewrite (SMART / INVEST)

Users must authenticate with email and password in under 2 seconds (p95) with up to 500 concurrent sessions. Given a registered user with valid credentials, When they submit the login form, Then a session is created within 2s and they land on the dashboard. Given 5 consecutive failed attempts within 10 minutes, When a 6th attempt is made, Then the account is locked for 15 minutes and an alert is logged.

Test case skeletons

positiveValid credentials authenticate within 2s
1. Open /login
2. Enter valid email and password
3. Submit the form
Expected: Dashboard loads and session cookie is set in under 2 seconds (p95).
negativeSixth failed attempt locks the account
1. Submit 5 invalid passwords within 10 minutes
2. Submit a 6th attempt
Expected: Account locked for 15 minutes, lockout message shown, security event logged.
boundary500 concurrent logins stay within SLA
1. Ramp to 500 concurrent login requests
2. Measure p95 latency
Expected: All logins succeed with p95 latency ≤ 2s and no 5xx responses.

Ask follow-ups without leaving the report

The clarification chat keeps your document and report in context — request more boundary cases, filter to security observations, or ask why REQ-004 was flagged, and new test cases land straight in the report.

Start analysing