Words From a Purple Mind

The testing methodology is very important in any organization. This document lays the foundation for the testing group. It’s main purpose is to set consistency and discipline to the testing process. It guides you through the process by defining why testing is being done, who is testing, what is produced during the various phases, and when it testing should be included in a project.

Software testing is not just limited to testing the application, it also includes documentation. Testing documentation is used for a variety of reasons:

• Explains the purpose & goal of testing
• Explains will be tested & how
• Provide testing results to the project team

I was cleaning out a folder on my machine when I stumbled on an oldie but goodie PDF called “Classic Testing Mistakes” by Brian Marick.

In the paper he states how he breaks the classic mistakes into 5 themes and how to resolve the mistakes:

Test Management tools are very important to any test team. Test teams use these tools to help capture requirements, design test cases, map test cases to requirements, test execution reports and much more. Companies may use one to many tools for this, which range from very expensive to open source. My advice would be to pick a tool that can meet most of your current and near future needs.

Alan Shalloway, CEO and founder of Net Objectives, presented on the lean software development principles and practices and how they can benefit to Agile practitioners during Agile 2008. For those of you that weren’t able to attend (like me) the video is definitely worth watching.