Difference between revisions of "Acceptance test"
| Line 3: | Line 3: | ||
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. | ||
| + | ==Definition== | ||
According to [[Juran's Quality Handbook by Defeo (7th edition)]], | 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. | :[[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. | ||
Revision as of 15:58, 3 July 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.
