This week we were assigned to read chapters 7 and 8 in The Clean Coder. Acceptance testing ensures that the code is working to standards according to the customer’s needs. This is important because sometimes requirements may be ambiguous and up for interpretation. These tests are put in place to set some sort of framework down so developers have something to work around. Sometimes after discussing with the customer, developers may have different ideas than what the customers actually want. Putting these tests in place is necessary because they act as “the perfect requirements document”.
Chapter 8 is about testing. Just because you have a QA department, does not mean you can leave all the errors in your code for them. You should aim for your code to be 100 percent error free when you pass it off the QA. It would be wise to work with QA to create unit tests, component test, integration test, system tests, and exploratory tests. It is important that you use all of these testing strategies to make sure your code stats bug and error free, and it working to standard.
Site Title 