لطفا منتظر باشید ...
Conclusion
Test your work. Test it often. Test it using built-in tests. Test it using automated tools. Test it using code reviews, inspections, and walkthroughs. Test and retest it. Reward those who find defects in your work by fixing those defects and thanking the finders for their efforts. Don't be defensive when your work comes under inspection. The process is about improving software quality; it's not a personal attack. When software quality improves, everybody winsnot just you and those connected with producing the software but everyone who uses the software too.
The purpose of testing is to mitigate the risk of failurefailure to ship high-quality software that meets customer needs. Testing reduces the risk of failure. Attaining 100% test coverage means you have zero risk of failure. Of course, you never reach zero risk, but you can certainly shoot for it. You can learn to manage the risk of failure down to an acceptable level using the techniques presented in this chapter.
