Difference between revisions of "Acceptance test"
(→Definition) |
|||
| Line 8: | Line 8: | ||
According to the [[BABOK Guide|BABOK Guide (3rd edition)]], | According to the [[BABOK Guide|BABOK Guide (3rd edition)]], | ||
| − | :[[User acceptance test]] ([[UAT]]). Assessing whether the delivered solution meets the needs of the stakeholder group that will be using the solution. The assessment is validated against identified acceptance criteria. | + | :'''[[User acceptance test]]''' ([[UAT]]). Assessing whether the delivered solution meets the needs of the stakeholder group that will be using the solution. The assessment is validated against identified acceptance criteria. |
==Related lectures== | ==Related lectures== | ||
Revision as of 04:57, 11 November 2020
Acceptance test (alternatively known as user acceptance test; hereinafter, the Test) is the derivative from the acceptance criteria that verifies whether a feature is functional. The test has only two results: pass or fail. Acceptance criteria usually include one or more 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.
Definition
According to Juran's Quality Handbook by Defeo (7th edition),
- Acceptance test. A highly structured form of testing a completed, integrated system to assess compliance with specifications; commonly applied to complex systems, such as computer systems.
According to the BABOK Guide (3rd edition),
- User acceptance test (UAT). Assessing whether the delivered solution meets the needs of the stakeholder group that will be using the solution. The assessment is validated against identified acceptance criteria.
