Difference between revisions of "Acceptance criteria"
(→Test) |
(→Related coursework) |
||
| Line 9: | Line 9: | ||
Test cases that users employ to judge whether the delivered system is acceptable. Each acceptance test describes a set of system inputs and expected results. | Test cases that users employ to judge whether the delivered system is acceptable. Each acceptance test describes a set of system inputs and expected results. | ||
| − | ==Related | + | ==Related lectures== |
*[[Business Analysis Quarter]]. | *[[Business Analysis Quarter]]. | ||
[[Category: Septem Artes Administrativi]][[Category: Articles]] | [[Category: Septem Artes Administrativi]][[Category: Articles]] | ||
Revision as of 12:28, 4 January 2019
Acceptance criteria (hereinafter, the Criteria) is the specification for a set of conditions that the product must meet in order to satisfy the customer. In Agile methodology, the product owner writes statements from the customer's point of view that explain how a user story or feature should work. In order for the story or feature to be accepted it needs to pass the Criteria; otherwise, it fails.
Test
- Main wikipage: Acceptance test
Acceptance test is the derivative from the Criteria that verifies whether a feature is functional. The test has only two results: pass or fail. The Criteria usually include one or more acceptance tests.
Test cases that users employ to judge whether the delivered system is acceptable. Each acceptance test describes a set of system inputs and expected results.
