Acceptance tests
Acceptance tests are written by the customer, or a proxy to the customer such as a product owner, where 'acceptance' refers to a quality gate that must be passed for the released software to be accepted as complete. Of course, your unit tests should be accepted too, but since they are at a very low level, it's unlikely you'll discuss them with your customer.
Now, the problem involves customers writing tests; the Gherkin syntax that we saw in Chapters 13 & 14 is one way of doing this.
Acceptance tests will often cover multiple processes, just like integration tests, and may run in a distributed environment to mimic production.
Acceptance tests are costly to build and maintain. Fortunately, they can be introduced gradually, ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access