Skip to main content
change system to integration tests
Source Link
Berin Loritsch
  • 46.5k
  • 7
  • 93
  • 164

Think of it this way:

  • Unit tests validate implementation
  • SystemIntegration tests validate design
  • Behaviors (BDD) validate specifications

You can have your one unit tested to 100% coverage documenting at least one reason for every line and branch you have in that unit. Then you combine that unit with something else that had different expectations for how your unit behaves. Behold an error in the design.

Think of it this way:

  • Unit tests validate implementation
  • System tests validate design
  • Behaviors (BDD) validate specifications

You can have your one unit tested to 100% coverage documenting at least one reason for every line and branch you have in that unit. Then you combine that unit with something else that had different expectations for how your unit behaves. Behold an error in the design.

Think of it this way:

  • Unit tests validate implementation
  • Integration tests validate design
  • Behaviors (BDD) validate specifications

You can have your one unit tested to 100% coverage documenting at least one reason for every line and branch you have in that unit. Then you combine that unit with something else that had different expectations for how your unit behaves. Behold an error in the design.

Source Link
Berin Loritsch
  • 46.5k
  • 7
  • 93
  • 164

Think of it this way:

  • Unit tests validate implementation
  • System tests validate design
  • Behaviors (BDD) validate specifications

You can have your one unit tested to 100% coverage documenting at least one reason for every line and branch you have in that unit. Then you combine that unit with something else that had different expectations for how your unit behaves. Behold an error in the design.