Five Agile Testing Approaches That You Should Know About

agile testing , which checks for bugs and performance bottlenecks within the agile workflow,  has different approaches and strategies. agile testing includes participation by many members of different it teams, with special expertise contributed by testers. the overall goal is to ensure the quality of the product, while keeping pace with rapid development and releases.

there has been a lot written about agile testing, and the related concepts of continuous testing and continuous quality. i recently came across some articles and blog posts that present a nice introduction to the topic of agile testing, and some of the challenges and strategies surrounding it. you’ll want to read these, as they provide valuable analysis and insight.

so with that said, let me list a few good ones.

1. agile testing vs traditional qa - this is an older post, but serves as a good introduction into some of the distinguishing characteristics of agile testing. venkatesh krishnamurthy is a senior technology architect and agile mentor who shares some of the challenges of traditional quality assurance and benefits of testing in agile, including ongoing feedback to developers and early identification of testing challenges and roadblocks, making it easier to overcome them.

2. continuous qa: bridging continuous integration and continuous delivery - kyle nordeen of zephyr takes a look at how continuous delivery and continuous integration are possible and where continuous qa fits into the equation. he writes that “the key to continuous qa is a strong test management strategy paired with agile testing methodologies.”

3. overcoming test automation challenges - lisa crispin argues that testers need technical awareness to collaborate effectively with all their team members, but software delivery teams already should have expert coders. she writes about some of the challenges of automation, including determining proper responsibility for automating, lack of time, and complexity of environments that make automation challenging.

4. how to overcome agile testing challenges - amir ghahrai, on his informative blog testing excellence, lists some of the most common testing challenges for qa in agile projects and how to overcome them. one point that i identified strongly with was to “start creating tests (automated or manual) as soon as possible so that when the feature is available for testing you can begin straight away.” make sure to also check out 12 qualities of a good agile leader.

5. the keys to mobile test automation that works - eran kinsbruner of perfecto mobile reveals some “must-haves” for building a continuous, unattended mobile test automation strategy that provides immediate feedback to its dev/qa teams - including that integration of different platforms is critical for cross-team collaboration.