One of the best descriptions of the hierarchy of tests that I have seen comes from “Growing Object-Oriented Software, Guided by Tests” by Steve Freeman and Nat Price.
1. Acceptance Tests: Does the whole system work?
2. Integration Tests: Does our code work against code we can’t change?
3. Unit Tests: Do our objects do the right thing, are they convenient to work with?
Can we now get on with some work, rather than discussing definitions ad nauseam?
#1 by felix on 21 March 2010 - 7:34 am
Quote
Well, I think the first one is a bit dodgy, as acceptance test is more to do with the contractual aspects of the development. What you are describing are System Tests…
Sorry
#2 by Tom on 21 March 2010 - 10:35 pm
Quote
Q.E.D.