Tuesday , January 23 2018
Home / Agile Software Development / 5 Ways Agile Testing Is Different from Traditional Testing

5 Ways Agile Testing Is Different from Traditional Testing

Some might argue that agile testing is the secret sauce that makes agile so effective at all. In an article for AgileConnection, Nishi Grover Garg attempts to distinguish what makes agile testing superior to traditional testing. She comes up with these five differences:

  1. Continuous involvement
  2. Essential tools
  3. Multidimensional skills
  4. Effective communication
  5. Quick feedback from testing

Test of Styles

In agile, testers are not some wholly separate group from the rest of the team. Instead, testers are involved constantly, as early as gathering requirements. They are incorporated such that they will report their needs or concerns to the scrum team first and to test managers second. Projects benefit as a whole from their additional input. This connects to the notion that agile testers need multidimensional skills, because they might be called upon to discuss tasks only tangentially related to testing.

Next, while extra tools might be optional in traditional testing, there are tools that are essential in agile testing. This is due to a higher demand for automation as a result of all the regression testing that comes from rapid iterations:

The same is true for test data generation, white-box testing tools, and static analysis tools, which become a necessity in an agile system. Given the time and quality constraints, performing white-box tests using control flow or data flow analysis, static analysis of code, or reviews for code and documents is no longer optional. Instead, it’s a mandate to prevent defects and ingrain quality into each work product.

It is kind of a stretch to say that traditional testing does not require effective communication, but it can be agreed that agile testing certainly requires communication more often. And lastly, regular testing bakes quality control into the project naturally, so there are no quality gateways waiting at the end. Feedback is always quick, which ideally means improvements come just as quickly.

You can view the original article here: https://www.agileconnection.com/article/5-ways-agile-testing-different-traditional-testing

About John Friscia

John Friscia is the Editor of Computer Aid's Accelerating IT Success. He began working for Computer Aid, Inc. in 2013 and continues to provide graphic design support for AITS. He graduated summa cum laude from Shippensburg University with a B.A. in English.

Check Also

Avoid ROI as a Basis for Prioritization

Business is all about ROI, and rightfully so, but ROI is not always a clear, …

Leave a Reply

Your email address will not be published. Required fields are marked *

Sorry, but this content
is for our subscribers only!

But subscribing to ACCELERATING IT SUCCESS is FREE and only one click away!
Join more than 40,000 IT Professionals and get the best IT management articles to your mailbox with Accelerating IT Success!

Unsubscribe at any time