Acceptance criteria verification
How codingassist reads the acceptance criteria of the work items linked to a pull request, judges each one against the change, and reports the result.
codingassist reads the acceptance criteria of the work items linked to a pull request, and the AI review judges whether the change satisfies each criterion. The result appears in the summary comment, next to the code findings.
How criteria are read
For each work item found (see Work items), codingassist takes the first non-empty field among:
- Acceptance Criteria (
Microsoft.VSTS.Common.AcceptanceCriteria) - Description
- Title
HTML is removed and each line becomes one criterion. No model is used for this step.
When the work item has a parent, for example the user story above a task, the parent's description and up to five of its criteria are added as context. The review is told that a change may cover only part of its parent.
How a criterion is judged
The criteria are part of the single AI review call of Stage 3, with the diff, the impact map and the static findings. For each criterion the model returns:
- whether the change satisfies it
- the evidence, in words
- a confidence between 0 and 1
The model judges the criterion against the diff it sees, up to 12,000 characters. It does not map a criterion to specific lines.
How the result is reported
The summary comment shows:
- the AC match score: satisfied criteria divided by all criteria
- an AC coverage section with each criterion and its status: satisfied, satisfied with low confidence (below 0.6), or not satisfied
A criterion that is not satisfied lowers the score. It does not fail the status check: only a Critical finding does.
When no work item is found
The code review still runs. The AC match score shows n/a and the summary says that no work item was linked.