A lot of automated acceptance testing pioneers have come around and denounced their fate in heavy automated test suites.
Acceptance tests are used to verify that a story (requirement) is complete. A normal usage scenario of a software product is defined by an acceptance test. There are various ways in which such scenarios can be described, either using a notation or some other approaches. However, the prime aim is to use an automation tool to execute such tests. The result of an acceptance test has a binary result, just like unit tests, i.e. pass or fail. Depending upon the maturity of the agile team, the term ‘functional test’, ‘acceptance test’, and ‘customer test’ are interchangeably used.
Acceptance tests are used to verify that a story (requirement) is complete. A normal usage scenario of a software product is defined by an acceptance test. There are various ways in which such scenarios can be described, either using a notation or some other approaches. However, the prime aim is to use an automation tool to execute such tests. The result of an acceptance test has a binary result, just like unit tests, i.e. pass or fail. Depending upon the maturity of the agile team, the term ‘functional test’, ‘acceptance test’, and ‘customer test’ are interchangeably used.
