Agile Testing = Test first in Agile Projects?

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.

Do you have a question?

Yes!

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

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

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