In chapter 7, Robert talks about the communication between professional developers and Businesses. When it comes to a project, there are a lot of information that is needed from both parties. Developers want to know exactly what they’re suppose to do for a project and businesses want to know exactly what they are going to get. This known as premature precision and most of the time this can never be communicated well. Robert mentions that that the best way to remove all ambiguity from the requirements is by doing acceptance tests. This is where stakeholders and developers collaborative writes a test to define when all requirements are actually done.
In opinion, i believe that acceptance testing is an effective solution to eliminate ambiguity between stakeholders and developers. If both parties can come to a consensus of what “done” actually means, then the communication should be great.
Chapter 8 talks about testing strategies. A developer’s should write their program well enough so that QA doesn’t find any bugs in them. Even though QA’s job is to help developers improve their code, developers should always strive to write clean code. It is a great mindset to maintain. This chapter also covers the benefit of the Test Automation Pyramid which list all the test that a professional organization need to write quality code. It includes Unit, component, integration, system, and manual exploratory tests. These tests covers all aspects of a program to ensure their cleanliness.