Peculiarities of Build Acceptance Testing

by Nataliia Vasylyna | January 13, 2015 10:00 am

Every software testing process includes build acceptance testing. It is a complex of tests that are run on each newly created build. The tests verify whether the module is ready for testing. If they pass, the build is verified further, if they fail, the programmers correct it and run the tests again.

Build Acceptance Tests Check:

• the main functions of the application module;
• whether the module is stable;
• whether there are no obvious serious or critical errors in the code.

The tests are focused on validation and acceptance of the build. Automated testing is usually applied for such verification.

Built acceptance testing sometimes is called smoke testing, but there is a difference between them. Smoke testing aims to verify only the main functions of the module, while build acceptance testing is more detailed, and usually comprises smoke testing of the module.

The tests are often included in regression testing and are executed on every new software build in order to make sure that the essential functionality operates as intended. They must be carefully elaborated and cover the main functions of the module. Experts in mobile application testing, desktop testing and web site testing claim that executing of build acceptance tests should not last longer than half an hour.

Related Posts:

• Acceptance Testing: How to Predict a Real-life Experience[1]
• Acceptance Criteria vs Acceptance Test[2]
• Briefly about System Testing[3]

Source URL: https://blog.qatestlab.com/2015/01/13/what-are-peculiarities-of-build-acceptance-testing/

---