Re: Role of stories vs specs, revisited

because if you have integration tests covering everything,
then you’ll know pretty quickly when your tests aren’t up to par.

If we have integration tests that cover everything then why have another
set of tests? At that point wouldn’t it simply be duplication and
wouldn’t it create more work for refactorings and such?

  ____________________________________________________________________________________

Looking for last minute shopping deals?
Find them fast with Yahoo! Search.
http://tools.search.yahoo.com/newsearch/category.php?category=shopping

On Jan 12, 2008 8:35 PM, Jay D. [email protected] wrote:

because if you have integration tests covering everything,
then you’ll know pretty quickly when your tests aren’t up to par.

If we have integration tests that cover everything then why have another set of tests? At that point wouldn’t it simply be duplication and wouldn’t it create more work for refactorings and such?

Jay - are you familiar with Acceptance Test Driven
Development/Planning and/or Test Driven Development?

Cheers,
David

This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs