Acceptance Criteria Vs Acceptance Tests in Agile
In Agile practice we defined acceptance criteria for each user story.
Just curious when we write acceptance tests, would that acceptance criteria be mapped one to one tp acceptance tests or we could have more test cases than number of acceptance criteria.
An acceptance criteria will map to one or more test cases. Since we still need to cover the negative tests. So in terms of total number of test cases, you'll have more than the acceptance criteria. It's not feasible to create every single negative test, and even less feasible to write them out as an acceptance criteria. However, you have to differentiate between acceptance tests and functional tests. An acceptance test will in generally be run with every delivery. While functional some functional tests will be deprioritized after the release, and not be run again until the next high risk change to that area.
Originally Posted by shabar
Hi Dlai, Thanks for your reply,
Originally Posted by dlai
Could you please give an example where one accepted criteria relates to more than one test case. Because I red some places that mentioned it needs to specify acceptance criteria even for negative scenarios.
Further in agile we normally write acceptance test for stories in test framework like Cucumber. But the when we suppose to write functional test for the same story? Is it going to be manual?
Last edited by shabar; 07-14-2014 at 02:44 PM.