InfoQ

InfoQ

News

My Bookmarks

Login or Register to enable bookmarks for unlimited time.

The content has been bookmarked!

There was an error bookmarking this content! Please retry.

Top Ten Reasons to Love Agile Testing

Posted by Mark Levison on Jun 03, 2009

Sections
Process & Practices
Topics
Agile Techniques ,
Agile
Tags
Quality ,
Acceptance Testing ,
Automation ,
Testing ,
Fun

Recently, Kay Johansen asked the question “Why you love Agile testing?” The responses varied from serious to the light hearted.

  1. No more manual test scripts! – Instead the scripts are run automatically leaving the tester more time to exploratory testing.
  2. Developers actually like me! – Finding problems before the iteration finishes and while the code is still fresh in the developer’s mind make it easier for them to find problems.
  3. Now I can break features before they're written! (both Kay and Philip) – With testing starting before the feature is written, the tester can prevent problems.
  4. Automated test results appear many times a day – providing rapid feedback after any changes.
  5. The atmosphere is very team oriented - (John Overbaugh) - Every team member cares about getting the testing finished not just the code (Lisa Crispin)
  6. Tester can fix the occasionally bug  (Lisa Crispin) - Everyone is comfortable since the automated tests
  7. Provides the opportunity to constantly review Test Practices (Adam Knight) – Instead of just repeating what has been done in the past, practices are frequently reviewed. In Adams case tests that used to take 5 days to run manually are down to 30 minutes now.
  8. I spend much, much less time debugging (Adrian Howard) - I get feedback almost as soon as I've made a mistake - so it's usually trivial to find and fix.
  9. The chance to actually impact quality instead of just documenting it! (John Overbaugh) – when the bugs are fixed immediately and not just put in a bug pile.
  10. There's always time for testing, because testing happens first - Josue Barbosa dos Santos tells the story of working in a government office in Brazil where the practice was to test at the end of the project. With development always behind schedule projects would reach the deadline and be released untested to users. By introducing TDD and ATDD at least some of the testing happens as the software is developed.

Kay’s number one reason to love Agile Testing: I get to hear people say "this is the best project I've ever worked on in my life!"

Thanks by Kay Johansen Posted
  1. Back to top

    Thanks

    by Kay Johansen

    Thanks for posting this - it's good to see all the contributions from the agile-testing list.

    -Kay

Educational Content

New-age Transactional Systems - Not Your Grandpa's OLTP

John Hugg discusses high volume transaction processing applications with high and low frequency profiles, and how VoltDB can be used for that purpose.

Cool Code

Kevlin Henney examines code samples to see what can be learned from them starting from the premise that one won’t write great code unless he knows how to read it.

Collaboration: At the Extremities of Extreme

Jason Ayers share the observations he made watching a team of developers collaborating in real time on the same code base, pushing XP, pair programming and continuous integration to their extremes.

Yesod Web Framework

Michael Snoyman presents Yesod, a web framework written in Haskell and containing a web server, templating, ORM, libraries (templating, gravatar, etc.).

Transactions without Transactions

Richard Kreuter and Kyle Banker on how to avoid classical RDBMS transactional systems by using compensation mechanisms, transactional messaging or transactional procedures.

Attila Szegedi on JVM and GC Performance Tuning at Twitter

Attila Szegedi talks about performance tuning Java and Scala programs at Twitter: how to approach GC problems, the importance of asynchronous I/O, when to use MySQL/Cassandra/Redis, and much more.

10 tips on how to prevent business value risk

One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.

Interview: Software Systems Architecture: Working With Stakeholders Using Viewpoints and Perspectives

InfoQ spoke to the authors of Software Systems Architecture on a couple of new topics, the System Context viewpoint and Agile, which have been added to the second edition.