I have not see these links explicitly stated in the Agile literature I have read. So, I was wondering if this approach was correct: Let a story be defined as “In order to [RESULT], [ROLE] needs to [ACTION]” then
- RESULT generates system tests.
- ROLE generates acceptance tests.
- ACTION generates component and unit tests.
Where the definitions are the ones used in xUnit Patterns which to be fair are fairly standard.
Is this a correct interpretation or did I misunderstand something?
1
Yes, that’s a pretty solid approach.
Role generating the acceptance tests may be a bit of a stretch, but at least it links the validation requirements to the presumed user of the feature (story).
Result and Action capture differing layers of verification, focusing on integration and unit testing. There can be a degree of overlap between those two aspects, but I think your approach works well enough.
Regarding xUnit Patterns book – if they are offering up templates, then they may well be within a hidden or secured site referenced within the book itself.
2