Related Content
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. |
||
Handling a Check Failure in Test Automation What happens on your team when a check (what some call “automated test”) fails? Regression tests or checks that are effective toward managing quality risk must be capable of sending action items outside the test/QA team quickly. How do you provide fast, trustworthy quality communications from your team? |
||
Test Design for Automation: Anti-Patterns Just like with design patterns, anti-patterns can benefit from a short and catchy name to make them easy to remember and talk about. Hans Buwalda shares a list of typical situations seen in tests that can harm automation and names for them. |
||
A Tester’s Guide to Dealing with Scrummerfall If you’ve been a tester on an agile team, you’ve probably experienced “Scrummerfall” behavior—a cross between Scrum and waterfall. There isn’t really any collaboration, and there's too much work in progress during each sprint. Bob Galen tells you how planning can help you avoid it. |
||
Providing Visibility into Testing Processes That Matter If the goal of a tester's customer report is to figure out what needs fixing, how close you are to shipping, or how much time you need to do additional testing, the metrics provided often don't give any of those answers. Matt Heusser tells you how and why you need to focus your information. |
||
Integrating Exploratory Testing into Product Design Exploratory testing, or ET, is a good fit for agile processes, can be done by any member of the dev/test team, and helps develop applications that map to customers' needs. Kevin Dunne writes how with increased use of ET, testing becomes an intellectual pursuit driving product quality and agility. |
||
Testing Customer Touchpoints When testing a product, it can be easy to neglect how support processes such as call verifications, email communication, online chat, and service request processes function. But these touchpoints go a long way toward defining customer experience and an organization in general. How can you improve? |
||
Software Testing: A Social Responsibility As businesses and consumers embrace big data and analytics, mobile, cloud, the IoT, and other rapidly emerging technologies, the expectation that software "just works" is rising exponentially. Equipping our technical workforce with the best education and training, tools, and approaches is critical. |