Supportsoft Glossary

Understanding Acceptance Testing in Software Projects

The last step to ensure that software is ready for a real work environment and used by its intended users is through acceptance testing. Acceptance testing checks to see if the [project] meets stakeholders’ expectations for the solution and that it aligns with the workflows these stakeholders requested originally.

Business Acceptance Testing (BAT) verifies that a software application serves the needs of the organisation internally and is performed by the organisation’s team. User Acceptance Testing (UAT), on the other hand, confirms that an application meets the intended users' (end users’) needs and wants. After a solution has undergone various stages of development, acceptance testing will be able to show whether there are any missing features or usability problems that will prevent the end users from using the application. Without acceptance testing, you run the risk of developing a solution that looks fine during an internal development process but is not suitable for the end user to use. Completing acceptance testing before going live can help improve the organisation’s confidence in the ability of the solution to support its business operations. A completed acceptance test indicates the product meets business goals and is technically sound to support real-world value.