Skip to main content
Version: 1.0.0

Acceptance Testing (v1.0.0)​

What is Acceptance Testing?​

Acceptance testing (AT) is a formal testing process that is conducted to determine whether a software system meets the requirements of the customer or end user. AT is the last phase of software testing, and it is conducted after all other levels of testing have been completed.

The purpose of AT is to ensure that the software system is acceptable to the customer or end user. This means that the system must meet the customer's or end user's needs and expectations. AT also helps to identify any defects or problems with the software system that may have been missed during earlier phases of testing.

Acceptance Testing Types:​

  • User acceptance testing (UAT): This is the most common type of AT. It involves the customer or end user using the software system in a way that simulates how they will use it in the real world.
  • Systematic testing: This involves using a set of predetermined test cases to test the software system.
  • Acceptance test-driven development (ATDD): This is a technique that combines AT with test-driven development (TDD). TDD is a software development process that involves writing unit tests before the code is written. ATDD extends TDD by adding acceptance tests to the mix.

Benefits of Acceptance Testing:​

  • It helps to ensure that the software system meets the needs and expectations of the customer or end user.
  • It helps to identify any defects or problems with the software system that may have been missed during earlier phases of testing.
  • It helps to improve the overall quality of the software system.
  • It helps to reduce the risk of defects and problems with the software system.
  • It helps to ensure that the software system is ready for release.

Acceptance testing is vital in ensuring software meets stakeholder demands and quality standards.