Acceptance Test Scenarios From a Spec
Turn a spec into test cases.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
[VERIFY] is an editorial flag, not a blank to fill. Wherever the prompt shows [VERIFY], check that item against a reliable source before you use it.
Create acceptance test scenarios. The feature spec: [SPEC]. Test environment and roles: [ENVIRONMENT_AND_ROLES]. Write test cases in a table: ID | Scenario | Preconditions | Steps | Expected result | Priority | Type (happy path, edge, negative, accessibility, performance). Include at least 20 scenarios covering the main flows, validation, permissions, error handling, concurrency, data limits, and recovery. Add exploratory test charters (three, each with mission, area, time box) and a regression checklist for related features. Identify spec ambiguities discovered while writing tests as a list of questions for the product owner. Provide a traceability mapping from requirements to tests with a coverage percentage (requirements with tests / total requirements, shown). Use only the spec provided; mark assumed behavior as [VERIFY]. Tag each scenario as automated, manual, or exploratory, mark the ten that must pass before release, and list the data and accounts the tester needs prepared in advance, such as a user with no permissions.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.