Acceptance test (software technology)
An acceptance test or acceptance test . In software engineering, user acceptance tests (UAT) are the checking of whether software functions as intended from the user's point of view and whether the user accepts the software. Software providers often test this with beta tests . It is not to be confused with a system test that ensures that the software does not crash and that the documented requirements are met.
General
Acceptance tests should be carried out by a subject matter expert, preferably the owner or customer of the software and, after the results have been summarized, should progress in development or revise the software. In software development, the acceptance test is one of the last phases of a project before the customer or user starts using the software. That is why the tests are carried out under realistic conditions.
The acceptance test acts as a final check of the required business functions and the correct functioning of the system under real operating conditions on behalf of the paying customer or a specific large customer. If the software works as requested and without problems under normal use, the same level of stability in production can be expected.
Acceptance tests are usually done by customers or end users, they don't focus on identifying simple issues like misspellings, cosmetic issues, and software crashes; Testers and developers identify and fix these problems in earlier unit tests, integration tests and system test phases.
The results of these tests give clients confidence in how the software will work after production. A passed acceptance test can also be a legal or contractual requirement for acceptance of the software.
Acceptance tests in extreme programming
Acceptance test is a term in agile software development methods, which is mainly used in extreme programming and relates to the functional test of a user story by the software development team in the implementation phase.
The customer specifies scenarios which are to be tested if a user narration has been carried out properly. A user narration may require one or more acceptance tests to ensure the functionality of the software. Acceptance tests are black box system tests .
Customers are responsible for checking the accuracy of the acceptance tests and checking the test results. In addition, if tests fail, they determine which of them have the highest priority. Acceptance tests are also used as regression tests before a production release. A user story is not considered complete if it fails the acceptance test. This means that acceptance tests have to be created for each run, otherwise the development team will not see any progress.
Course of an acceptance test
- Analyze customer requirements
- Create test scenarios
- Define test plan
- Create test cases
- Perform acceptance test
- Record test results
- Indicate whether the customer requirements are met
Individual evidence
- ↑ Cimperman, Rob (2006). UAT Defined: A Guide to Practical User Acceptance Testing. Pearson Education. Chapter 2. ISBN 9780132702621 .
- ^ Goethem, Brian Hambling, Pauline van (2013). User acceptance testing: a step-by-step guide. BCS Learning & Development Limited. ISBN 9781780171678 .
- ↑ Pusuluri, Nageshwar Rao (2006). Software Testing Concepts And Tools. Dreamtech Press. p. 62. ISBN 9788177227123 .
- ^ "Introduction to Acceptance / Customer Tests as Requirements Artifacts" . agilemodeling.com. Agile modeling. Retrieved December 9, 2013.
- ↑ Don Wells. "Acceptance Tests". Extremeprogramming.org. Retrieved September 20, 2011.