Related Content
 |
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 Suite In 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. |
|
 |
Calculating the Cost of Failure What is the cost to your business of an outage due to a major bug? Usually it's calculated as mean time between failures multiplied by mean time to recovery. But what if you could deploy to a limited number of users and monitor effects? Then the equation includes a third variable: number of users impacted. |
|
 |
Is It Time to Say Goodbye to Manual Testing? Automation helps you save time and make ideal use of your resources with constant and ongoing test executions. However, there are certain testing scenarios where automation does not prove handy. How important are these scenarios? Is automation great enough to warrant making manual testing a thing of the past? |
|
 |
Google’s Magic Metric Google has a "magic metric" that determines where effort should be spent, based on the fact that the number of hits on every site with one of its ads is directly correlated to revenue. Most companies do not have a magic metric, so they search for a way to measure process. How can you change the conversation? |
|
 |
Promoting Sustainable Test Automation Truly sustainable test automation imparts minimal impact on people and processes over the years. It is achieved by deploying automation frameworks that shield testers and processes from the automation tools and technologies that are constantly evolving. Carl Nagle tells you how to attain long-term success. |
|
 |
Jelly Beans and Defect Classification: Different Strategies for Success When there’s a bowl of jelly beans, some people grab a few at random, but most of us have favorites. If you're crafty and have flexible standards, you can maximize consumption by adjusting your criteria as colors dwindle. Classifying defects should not be like choosing jelly beans; you need firm standards. |
|
 |
Stronger, Faster Quality with Simple, Focused Checks Imagine focusing on prioritized business requirements at the software layer closest to where those business items are implemented. Writing just one check—that is, a programmed verification—per business requirement makes for simple, focused checks, supporting stronger, faster quality around the team. |
