This week's book giveaway is in the Reactive Progamming forum.
We're giving away four copies of Reactive Streams in Java: Concurrency with RxJava, Reactor, and Akka Streams and have Adam Davis on-line!
See this thread for details.
Win a copy of Reactive Streams in Java: Concurrency with RxJava, Reactor, and Akka Streams this week in the Reactive Progamming forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Liutauras Vilda
  • Junilu Lacar
  • Jeanne Boyarsky
  • Bear Bibeault
Sheriffs:
  • Knute Snortum
  • Tim Cooke
  • Devaka Cooray
Saloon Keepers:
  • Ron McLeod
  • Stephan van Hulst
  • Tim Moores
  • Tim Holloway
  • Carey Brown
Bartenders:
  • Piet Souris
  • Frits Walraven
  • Ganesh Patekar

Agile Testing:How does it help in the proactive way of avoiding bugs?

 
Ranch Hand
Posts: 72
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,

I wished to know whether agile testing can be used in a proactive way to avoid the bugs in sofware projects?

Thanks,
Piya
 
Bartender
Posts: 10336
Hibernate Eclipse IDE Java
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
All testing is (by nature) reactive. Not sure how you proactively test for anything? I suppose the only proactive part is the up front acknowledgment that there will be defects in your code perhaps?
 
Author
Posts: 31
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Actually, testing in an agile way is all about preventing bugs. We encourage testers to be working with the whole team during planning sessions to question, uncover hidden assumptions, etc. If descrepenices are talked about early, then many of the bugs never arise - they have been prevented.

Both Lisa and I have mentioned the agile testing quadrants in previous answers. The 2 left hand quadrands are tests that support the team to encourage the developers to code the right stuff. These "tests" are written before a single line of code is written. Once a team gets good at this, often the only bugs found are the ones which no one even thought of before... that is where exploratory testing comes into play.


Janet
 
blacksmith
Posts: 979
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

Janet Gregory wrote:Actually, testing in an agile way is all about preventing bugs. We encourage testers to be working with the whole team during planning sessions to question, uncover hidden assumptions, etc. If descrepenices are talked about early, then many of the bugs never arise - they have been prevented.

Both Lisa and I have mentioned the agile testing quadrants in previous answers. The 2 left hand quadrands are tests that support the team to encourage the developers to code the right stuff. These "tests" are written before a single line of code is written. Once a team gets good at this, often the only bugs found are the ones which no one even thought of before... that is where exploratory testing comes into play.



Hi Janet,

I hope you don't mind, since you are in the spotlights, but I would like to point to an interesting Google techtalk of Mary Poppendieck: Competing on the basis of speed

She mentions the quadrants and the preventive testing approach...

Cheers,

Gian
 
You didn't tell me he was so big. Unlike this tiny ad:
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koop
https://coderanch.com/wiki/718759/books/Building-World-Backyard-Paul-Wheaton
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!