Description
Problem
In Agile teams, User Stories often reach “Ready for Test” with incomplete Acceptance Criteria (AC), unclear validations, missing error handling, or undefined edge cases. QA spends time chasing clarifications late in the sprint, causing rework and test delays.
What the automation does
1. Trigger starts when a User Story moves to Ready for Test (or QA runs manually with Work Item ID).
2. UiPath fetches story details from ADO (Title, Description, AC, links).
3. AI generates a review in a fixed template:
• Missing info / questions (Must Clarify)
• Ambiguities (vague terms, missing expected results)
• Negative cases
• Boundary/edge cases
• Non-functional risks (performance, security, accessibility, logging)
4. UiPath posts the output as a comment in ADO Discussion.
5. Optionally adds tag AI-Req-Reviewed and logs execution.
Benefits
• Faster and consistent requirement reviews
• Fewer blockers during test design/execution
• Better coverage of negative/boundary scenarios
• Improves sprint predictability and reduces escaped defects
Where it fits in QA process
Requirements → Test Design → Review → Execution → Signoff
(Use Case targets Requirements stage)
Link
Date
2025-12-19
Related UiPath products
AI Center
Apps
Automation Cloud
Integration Service
Orchestrator
Studio
Test Suite