In the 7th chapter “Acceptance testing” author Martin discuss about the communication aspects between programmers and stakeholders. Then he drives into the essentials of having acceptance tests to narrow the communication gap. Martin argues that in reality, the communication of requirements is extremely difficult. Because of which both programmers and stakeholders often falls into various miscommunication traps such as premature precision, estimation anxiety, and late ambiguity. Then Martin suggests a solution: is to write automated acceptance tests. Acceptance tests helps to define when a requirement is ‘done’. Due to cost reason acceptance tests should always be automated. Professional developers should take responsibility for their part in ensuring that acceptance tests are automated.
Furthermore, Martin clearly states acceptance tests not being the same as unit tests. Although they may test the same things, they do so through different mechanisms and pathways. Unit tests validate the system from the developer’s point of view whereas acceptance tests validate the system from the business and QA points of view.
Moreover, the chapter talks about the challenging to write acceptance tests for GUI. Alongside suggests the solution to design the system so that you can treat the GUI as though it were an API.
I personally know how to write unit tests as being a programmer. I don’t have any experience as of now as a stakeholder. From my part I will definitely make sure that the tests are fully automated and easier for non-programmers to understand. I will specify all the details during my testing phase for the stakeholders to ensure that the system they are paying for really does what they need.
The next Chapter “Testing strategies” revolves around the disciplines of Test Driven Development. Author explains about unit, component, integration, system, and manual exploratory tests. The test automation pyramid diagrams summaries the concept of those test. Author argues that unit tests provide as close to 100% coverage as is practical. As good as it is to have a suite of unit and acceptance tests, higher-level tests are needed to ensure that QA finds nothing.
I am not exposed to any other tests rather than unit. I will definitely work together with QA team to ensure the quality of the system.

From the blog CS@Worcester – Software Dev Capstone by osworup007 and used with permission of the author. All other rights reserved by the author.