Tag Info

New answers tagged

2

I think you have it backwards - the integration test is the "real" test, testing the system as a whole. But as it is a slow and often difficult to setup, we have unit tests as a stop-gap measure. They test bits in isolation which should give you an indicator that the code will probably work correctly when sent to the integration test. You can write working ...


8

It sort of seems like a test that says, "yes, your production code is actually working when you don't stub or mock things out." That's exactly what it is. Stubs and mocks isolate the infrastructure from your unit tests, which means that your units get tested, but not the infrastructure that you've stubbed out, nor the connections your units make with ...



Top 50 recent answers are included