Related Content
 |
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? |
|
 |
Why Problems Are Good Many large enterprise technology systems have suffered incidents that had significant impact to the customers as well as the firm itself. But experienced IT professionals know that learning from our mistakes is good, and so, too, is harnessing the lessons learned from a serious incident or problem. |
|
 |
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. |
|
 |
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. |
|
 |
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. |
|
 |
Building an Effective Lean Testing Strategy Lean testing strategies can help QA teams effectively mitigate wasted resources and ensure that they are giving each project the attention it deserves. Sanjay Zalavadia details some strategies QA teams should implement in order to create an effective lean testing practice for their operations. |
|
 |
Scalability of Tests—A Matrix Hans Buwalda highlights the scalability of unit, functional, and exploratory tests—the three kinds of tests used to verify functionality. Since many automation tools and strategies traditionally focus on functional testing, Hans provides some strategies to make functional testing more manageable. |
