wood burning stoves 2.0*
The moose likes Agile and Other Processes and the fly likes Agile Testing = Test first in Agile Projects? Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Murach's Java Servlets and JSP this week in the Servlets forum!
JavaRanch » Java Forums » Engineering » Agile and Other Processes
Bookmark "Agile Testing = Test first in Agile Projects?" Watch "Agile Testing = Test first in Agile Projects?" New topic
Author

Agile Testing = Test first in Agile Projects?

Matthias Merz
Greenhorn

Joined: Oct 31, 2008
Posts: 9
I thought that in an agile aproach it would be very straight forward to use test first if you care about testing at all :-)

You need test for each sprint to check if the sprint was successful and everything has been implemented in a sufficent quality. No need to wait. Just write the tests at the beginning of the sprint. That way, the developers think before they implement and a "tester" or quality manager can confirm the effectiveness of the test suite.
Ilja Preuss
author
Sheriff

Joined: Jul 11, 2001
Posts: 14112
Do you have a question?


The soul is dyed the color of its thoughts. Think only on those things that are in line with your principles and can bear the light of day. The content of your character is your choice. Day by day, what you do is who you become. Your integrity is your destiny - it is the light that guides your way. - Heraclitus
Matthias Merz
Greenhorn

Joined: Oct 31, 2008
Posts: 9
Yes!

Would you agree with this statement (Agile Testing = Test first in Agile Projects)?

If not, then what is your idea of Agile Testing?
Lisa Crispin
Ranch Hand

Joined: Feb 03, 2009
Posts: 43
Matthias Merz wrote:Yes!

Would you agree with this statement (Agile Testing = Test first in Agile Projects)?

If not, then what is your idea of Agile Testing?

Agile testing is a pretty vast topic, as we discovered in writing a 500-page book about it (which still doesn't cover everything!)

We certainly have had good success in using tests, both at the unit and acceptance/business-facing level, to drive coding, and we explain how to do this in the book.

Even so, there are lots of situations where post-development testing is still appropriate. Exploratory testing on the "finished" code is important to learn where it might have deficiencies or need enhancements, which may feed into more new stories. That's just one example.
-- Lisa


Co-author, with Janet Gregory: Agile Testing: A Practical Guide for Testers and Agile Teams (Addison-Wesley, 2009) http://lisacrispin.com
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Agile Testing = Test first in Agile Projects?
 
Similar Threads
Agile Adoption in Traditional Maintenance
resources (links,books) for topic software estimation?
How to incorporate QA into an agile project?
Agile methodology - not relevant to all projects
Testing vs. agile manifesto?