Writing user-facing tests
Acceptance tests are written with users and should be comprehensible to users. This is why the choice of a method for writing them depends on who the customer is.
For example, imagine a purely technical person. If you write a web service that optimizes the database storing, and your system is used only by other systems and read only by other developers, then your tests can be expressed in the same way as unit tests. As a rule, the test is good if understood by both, developer and user.
In real life, most software is written to deliver a specific business value, and that business value is defined by non-developers. Therefore, we need a common language to collaborate. On one side, there is the business who understands ...
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