The best role for the QA part of the team is to act as specifiers and characterizers. Rather, QA and Development should be working together to ensure the quality of the system. The previous section might have made it seem that QA and Development are at odds with each other, that their relationship is adversarial. They should ask themselves how it happened and take steps to prevent it in the future. Still, every time QA finds something the development team should react in horror. Of course, it's not likely that this goal will be constantly achieved. Despite the fact that your company may have a separate QA group to test the software, it should be the goal of the development group that QA finds nothing wrong. I've said this before, and I'll say it again. What every professional development team needs is a good testing strategy. Writing these tests is a good thing, but it is far from sufficient. But testing is not simply a matter of writing a few unit tests or a few acceptance tests. Here we gathered and summarized the main tips from the eighth chapter.
This is the eighth article from the series 'Tips from The Clean Coder'.
