How do you write acceptance criteria for an AI coding task?
Acceptance criteria replace “make it work nicely” with a specific starting condition, an action and an observable result. Include the visible failure and retry behavior as well as the happy path.
How to check it
- Specify input boundaries: empty field, valid value and overlong text.
- State which record or screen must change on success.
- Describe what should happen when the same action is repeated.
Concrete example
Example: a valid application creates one record; a rejected request preserves input and shows an error; double-clicking does not create a second application. Evidence is the real response and record identifier.
Avoid a false conclusion
A test name alone is not a criterion. Explain which behavior it proves and which conditions remain outside its coverage.
Reference
VCT Editorial