BT

New Early adopter or innovator? InfoQ has been working on some new features for you. Learn more

Agile Development Races Ahead of Traditional Testing

| by Savita Pahuja on Apr 29, 2014. Estimated reading time: 1 minute |

Agile practices are breaking apart traditional testing organizations. Agile developers invariably perform more testing so QA professionals need to involve in the daily operations of the development team mentioned by Diego Lo Giudice, principal analyst at Forrester Research, in his recent blog on Why agile development races ahead of traditional testing.

As per Deigo in this recent trend, QA professionals should focus more on advance testing practices. 

They need to adapt to changing circumstances by getting deeply involved in the Advanced practices such as test-driven development, increased testing automation and continuous build and integration make a significant impact on the day-to-day activities of developers and testers.

Separate testing and developers team doesn’t fit into agile work environment, stated by Deigo.  

When testing teams are separated from development, it is typical for testers to try to find as many bugs as possible – but only after the developers have written the code……

Segregating testers from developers makes it hard to integrate their work into a continuous delivery pipeline. 

Lisa Crispin,co-author of “Agile Testing: A Practical Guide for Testers and Agile Teams”, delivered a session on Changing your testing mindset at Booster Conference, Bergen, Norway, 2014. She focused on more collaboration between developers and testers.

Instead of…We are here to find bugs or ensure requirements are met or break the software

Think how do we “bake quality in”?

Deigo mentioned why traditional testing lags behind agile.

  1. Large volumes of manual test activities slow down delivery.
  2. Teams only start testing once they have developed and integrated the system. Unfortunately, projects often fall behind schedule, so teams compress and sacrifice the activities left at the end.
  3. Teams build up too much technical debt. One sure-fire killer of on-time delivery is finding out late in the development cycle that your application has major quality problems. Late discovery of defects lead to high rates of rework and waste.

Because of these reasons a shift is important in testing to comply it with agile development. These shifts in testing practices also change how development teams select testing tools. Deigo shared his views on testing tools

Developers want tools that easily plug into their integrated development environments (IDEs), while QA and other software professionals prefer tools that offer a higher level of abstraction and are easy to use.

 

 

Rate this Article

Adoption Stage
Style

Hello stranger!

You need to Register an InfoQ account or or login to post comments. But there's so much more behind being registered.

Get the most out of the InfoQ experience.

Tell us what you think

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread
Community comments

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread

Discuss

Login to InfoQ to interact with what matters most to you.


Recover your password...

Follow

Follow your favorite topics and editors

Quick overview of most important highlights in the industry and on the site.

Like

More signal, less noise

Build your own feed by choosing topics you want to read about and editors you want to hear from.

Notifications

Stay up-to-date

Set up your notifications and don't miss out on content that matters to you

BT