Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

4
  • You say: "unit tests ... above this lies your integration tests" -- however, the post I link to says "Integration Tests: Automate the entire system" ... this doesn't sound as if integration tests lie above unit tests. Commented Oct 4, 2011 at 13:35
  • 3
    @Martin: From the linked post: If you automate this sort of testing in order to detect breakages when they happen in the future, it’s called integration testing. AFAIK, this statement is wrong, this is the definition of regression testing. Integration testing is exactly as Thomas says, one level above unit testing (you test how well your units integrate into a system). Commented Oct 4, 2011 at 13:57
  • @Martin That post gets a few definitions and concepts, including TDD and integration testing, wrong, at least based on the standard definitions that I've learned. Commented Oct 4, 2011 at 14:08
  • 1
    +1 thomas - this is an extremely common misconception; TDD tests scale, unit through acceptance, because they test features, not modules. Should never have called them 'unit' tests, too confusing! Commented Oct 5, 2011 at 3:00