Related Content
 |
What's Your Story? How Testers Add Value Testers have a story. It involves the kind of information we gather, the way we gather it, whom we tell, and what decisions are impacted by it. Management has their own story, but sometimes the goals are different. Find out the story your executives have for testing, and see what value it brings. |
|
 |
Optimizing Testing: Moving Faster without Compromising Quality At some point as a tester, you’ve probably been urged by management to reduce the amount of time required for testing without compromising product quality. How can you possibly do that? Weighing the added value and relative importance of each testing task can help you optimize your testing strategy. |
|
 |
The Vocabulary of Testing Testers in every project and company spend time defining and debating the meaning of common testing terms. Which labels are used for testing activities tend to vary from team to team. How do you reach an understanding? Dawn Haynes addresses the disparities and highlights what's really important. |
|
 |
Part of the Pipeline: Why Continuous Testing Is Essential With the DevOps movement and push for continuous delivery, the way we have done test automation in the past must evolve. In continuous testing, tests are run as part the build pipeline so that every check-in and deployment is validated. Learn more to ensure your team can achieve continuous testing. |
|
 |
Why Automation Will Never Replace Manual Testing Manual testers are experts at the unexpected, while automation is all about predictability. Automation won’t replace manual testing, but neither will manual testing replace automation. Linda Hayes writes that once the difference between them is understood, the fear of automation dissolves. |
|
 |
Managing Security Testing in Agile Software Development One of the biggest myths in the world of agile development is that there is not enough time to do security testing. Sanjay Zalavadia shows you the most efficient and cost-effective way of performing security testing in an agile environment: by rolling it into each sprint incrementally, from day one. |
|
 |
Test Automation Gets No Respect The conventional approach to software automation for quality creates a losing situation for the people doing the work. When tests are reliable or take more time than first estimated, management and the rest of the team lose confidence. How can you produce consistently quick, quality information? |
|
 |
The Word “Automation” Has Led Us Astray The misunderstanding that automation for software quality is just doing what humans do (i.e., manual testing), but faster and more often, causes business risk. Unless you’re very clear, the quality measure is incomplete. The word automation distracts from the real value: measuring quality. |
