Difference between revisions of "Acceptance test"

From CNM Wiki
Jump to: navigation, search
(Definition)
 
Line 1: Line 1:
[[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''.
+
[[Acceptance test]] (when performed by an [[end-user]], also 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.
+
[[Test case]]s that users employ to judge whether the delivered system is acceptable. Each acceptance test describes a set of system inputs and expected results.
  
==Definition==
+
 
 +
==Definitions==
 
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.
Line 10: Line 11:
 
:'''[[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==
+
==See also==
*[[Validated Learning Quarter]].  
+
 
 +
===Related lectures===
 +
:*[[Verification vs Validation]].
 +
:*[[Validated Learning Quarter]].  
  
[[Category: Septem Artes Administrativi]][[Category: Articles]][[Category: Quality Management]][[Category: Business Analysis]]
+
[[Category: CNM Cyber Placement]][[Category: Septem Artes Administrativi]][[Category: Articles]][[Category: Quality Management]][[Category: Business Analysis]]

Latest revision as of 04:59, 11 November 2020

Acceptance test (when performed by an end-user, also 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.


Definitions

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.

See also

Related lectures