Acceptance Test
An Acceptance Test is a system test conducted to determine whether system's requirements are met.
- AKA: Integration Test, User Acceptance Test (UAT), End-User Test, Operational Acceptance Test (OAT), Field Acceptance Test.
- Context:
- It can range from being a Formal Acceptance Test to being a User Acceptance Test.
- It can be an input to an Integration Test Task.
- …
- Example(s):
- Counter-Example(s):
- a Unit Test.
- a Chemical Test.
- a Physical Test.
- See: Smoke Testing (Software), Specification, Contract, Performance Test (Assessment), Systems Engineering, Black-Box Testing, Software System.
References
2016
- (Wikipedia, 2016) ⇒ http://wikipedia.org/wiki/Acceptance_testing Retrieved:2016-2-22.
- In engineering and its various subdisciplines, acceptance testing is a test conducted to determine if the requirements of a specification or contract are met. It may involve chemical tests, physical tests, or performance tests.
In systems engineering it may involve black-box testing performed on a system (for example: a piece of software, lots of manufactured mechanical parts, or batches of chemical products) prior to its delivery. In software testing the ISTQB defines acceptance as: formal testing with respect to user needs, requirements, and business processes conducted to determine whether a system satisfies the acceptance criteria and to enable the user, customers or other authorized entity to determine whether or not to accept the system. Acceptance testing is also known as user acceptance testing (UAT), end-user testing, operational acceptance testing (OAT) or field (acceptance) testing.
A smoke test may be used as an acceptance test prior to introducing a build of software to the main testing process.
- In engineering and its various subdisciplines, acceptance testing is a test conducted to determine if the requirements of a specification or contract are met. It may involve chemical tests, physical tests, or performance tests.