Win a copy of Svelte and Sapper in Action this week in the JavaScript 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
  • Ron McLeod
  • Paul Clapham
  • Bear Bibeault
  • Junilu Lacar
Sheriffs:
  • Jeanne Boyarsky
  • Tim Cooke
  • Henry Wong
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • salvin francis
  • Frits Walraven
Bartenders:
  • Scott Selikoff
  • Piet Souris
  • Carey Brown

Agile Testing = Test first in Agile Projects?

 
Greenhorn
Posts: 9
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
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.
 
author
Posts: 14112
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Do you have a question?
 
Matthias Merz
Greenhorn
Posts: 9
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Yes!

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

If not, then what is your idea of Agile Testing?
 
Ranch Hand
Posts: 43
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

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
 
Whoever got anywhere by being normal? Just ask this exceptional 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
    Bookmark Topic Watch Topic
  • New Topic