Overview: 

Ten Tips of Agile Testing

After years of doubt and skepticism, the principles of Agile are now accepted by development teams worldwide. But the increased flexibility and adaptability of Agile poses some tough challenges for QA teams.

With the Agile methodology, development now works in small cycles – planning and designing only far enough ahead to keep the flow working. With this increased flexibility, the burden of excessive formal documentation was greatly alleviated – but not for test teams. We'll show you how testing can now be incorporated into each step of the process, not just at the end of each release. Other topics include:

The Emergence of "Agile-Fall"

Although Agile is gaining in popularity, this piece is not an endorsement of one methodology over the other. Many of the tips we’ll discuss in this whitepaper are based on Agile concepts, but are relevant to both types of development processes. So, if your organization uses traditional waterfall methodologies, you can still benefit from Agile concepts to improve quality. This condition has been coined as “Agile-fall.” “There’s no shame in that if that’s what works,” said testing expert John Bach. “When you’re going through a transition from waterfall to agile, that may be the best approach ...continue reading...

.

How to Define Your QA Matrix

Defining the coverage requirements is an essential part of the specifications process and should be dealt with at an early stage. Defining it clearly and early helps management allocate resources and determine what can be done in-house versus what should be outsourced for greater coverage. Unless your software is designed for a simple and homogenous audience that’s identical to your in-house QA team, it’s likely that you have gaps in your testing coverage. Yet to fill these voids in-house – whether they be browser, OS, location, language or device – would be impractical ...continue reading...

How to Capture Meaningful Data

Testing managers often focus on information that is of little use to anyone but themselves - keep this in mind when collecting and analyzing data. We’re all used to compiling detailed reports that show the number of test cases written (i.e. how many have been run, failure rate, severity levels, etc.) and this is certainly valid data to the testing manager, but who else in your organization will care? One type of data that would be of value is direct business impact statistics: Sales missed due to bugs, customer renewal rate and relative cost of defect. This type of information is ...continue reading...

Get the rest of the story >>>