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.
Software developers often distinguish acceptance testing by the system provider from acceptance testing by the customer (the user or client) prior to accepting transfer of ownership. In the case of software, acceptance testing performed by the customer is known as user acceptance testing (UAT), end-user testing, site (acceptance) testing, or field (acceptance) testing.
A smoke test is used as an acceptance test prior to introducing a build to the main testing process.
Read more about Acceptance Testing: Overview, Process, User Acceptance Testing, Acceptance Testing in Extreme Programming, Types of Acceptance Testing, List of Development To Production (testing) Environments, List of Acceptance-testing Frameworks
Famous quotes containing the words acceptance and/or testing:
“Most women of [the WW II] generation have but one image of good motherhood—the one their mothers embodied. . . . Anything done “for the sake of the children” justified, even ennobled the mother’s role. Motherhood was tantamount to martyrdom during that unique era when children were gods. Those who appeared to put their own needs first were castigated and shunned—the ultimate damnation for a gender trained to be wholly dependent on the acceptance and praise of others.”
—Melinda M. Marshall (20th century)
“Traditional scientific method has always been at the very best 20-20 hindsight. It’s good for seeing where you’ve been. It’s good for testing the truth of what you think you know, but it can’t tell you where you ought to go.”
—Robert M. Pirsig (b. 1928)