test management
|
Where Do Software Bugs Come From?There's much more to bugs than either a programmer screwed up or there are missing or misunderstood requirements. Many more possibilities could be responsible. A good tester warns that these areas are unknown; a great tester might even test for them. Look over your bug trackers and see what you can learn. | 
Matt Heusser |
|
Why Your Test Efforts Should Tackle Data FirstAutomation projects often start by tackling the technical issues, but Linda Hayes says a specific data environment should be established first. If you can’t control, define, and predict your data, you won’t have the repeatability that makes test automation practical—but it makes sense for manual testing, too. | 
|
|
Creating a Test Strategy and Design for Testing DataThese days, data comes from multiple sources, is transformed in many different ways, and is consumed by hundreds of other systems, so we must validate more data, more quickly. Mike Sowers shares his work in progress checklist for things to consider when developing a test strategy and design approach for data. | 
|
|
Automate for Efficiency: How Test Automation Does More than Spot Bugs Some form of automation should be used to streamline testing, but leveraging automation as a crutch won’t help you or your team spot every bug and produce high-quality software. In automation, the tools don’t do all the testing—they simply do what they are told to do by the actual tester. |
|
|
When and When Not to Automate Automation integration is a huge value to QA teams, but not everything can or should be automated. By understanding the difference, teams will be able to utilize their tools more effectively and streamline operations for better results. Sanjay Zalavadia looks at when and when not to automate. |
|
|
The Tester as Product OwnerA lot of the bugs we find were never thought through in the first place. Many of these situations are preventable, yet instead of prevention, we get the tester playing the role of the product owner—and playing it late. Why is it that we never have time to do it right, but we always have time to do it over? | 
|
|
How Do We Sell the “Test Early” Principle? Many companies are striving to test earlier. But goals and principles are always easier to articulate than they are to implement. Often, this is less of a technical issue and much more an organizational, change management challenge. Michael Sowers talks about the steps to take to make things happen. |
|
|
The Benefits of Continuously Optimizing Your Regression Test SuiteIn any project, for a quality product or application rollout, regression testing plays a key role. The challenge comes with regularly examining your regression suite and making sure it is running optimally. The optimization process should be implemented with every major release to ensure efficient testing. | 
|