by Nadine Parmelee and Brenda Hall
When you’re testing software, the software you are testing and the tools you use change, but the process of how you test remains constant. Sometimes you may apply different styles and different types of tests to different projects, but for the most part, testing is testing – you put your test data in and check your expected result, you manipulate a menu or control and check your expected result.
How different companies and even how different project teams approach testing, though, is very different. I have personally seen everything from a very rigid and formal process with no room for change to “anything goes” with testing as more of an afterthought. What most project teams need is to find balance somewhere in the middle of the two extremes.
Having a test process is important to testing
- To make sure test results are reproducible
- To know how much testing is complete
- To know how much more testing is needed
- To understand what will and will not be tested
- To have an idea of the quality of a product Continue reading