Azure DevOps User Story With Acceptance Criteria and Test Cases
Write a story and matching test cases for Test Plans.
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.
Write an Azure DevOps user story and matching manual test cases for this feature: [FEATURE_DESCRIPTION]. Users and permissions: [USERS]. Business rules: [BUSINESS_RULES]. Systems touched: [SYSTEMS]. Give the title, description and acceptance criteria (Given/When/Then) with codes such as AC1. Then write test cases with title, preconditions, numbered steps with an expected result for each step, priority, and the criterion code each checks. Cover the main path, a validation error, a permission case and a boundary case. Write steps so a tester who has not seen the feature can follow them, use [TEST DATA] placeholders instead of real data, and state expected results as observable facts, such as the message 'Saved' appears, rather than 'it works'. List assumptions and unanswered questions separately, add a note on which existing tests to rerun for regression, and mark anything that depends on how our Test Plans are configured [VERIFY]. Keep the story small enough for one sprint, and say if it should be split. Put the test cases in a table if that helps me copy them into the test plan.
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.