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 wins—not 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 failure—failure to ship high-quality software that meets customer needs. Testing reduces the risk of failure. Attaining 100% test ...
Get Guru's Guide to SQL Server™ Stored Procedures, XML, and HTML, The now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
