Not quite. Not always. I remember really many cases when integration tests are not needed simply because that specific integration logic will be checked with any single smoke test.
To be more precise the situation on the photo has absolutely nothing to do with integration testing. It would fail exactly the same in case of unit test like "put the car on top of the box and lift it".
Latest comments (17)
I was having trouble explaining integration vs unit test to my mentee once, and I showed her a couple of these jokes and she instantly understood.
Don't trust the user, add validation.
Expected behaviour
Users. If we could only do without them, what a wonderful world it could be :-)
Not quite. Not always. I remember really many cases when integration tests are not needed simply because that specific integration logic will be checked with any single smoke test.
To be more precise the situation on the photo has absolutely nothing to do with integration testing. It would fail exactly the same in case of unit test like "put the car on top of the box and lift it".
Just handle exceptions properly.
Why,docker, why???
Use CTRL+R
2 unit tests and 1 integration test but needed a 2nd with the input order flipped
Input fail due errors is vswr
Depend on described use cases, this is undocumented user behavior!
This is great!
Clear cache and try again π
π€£π€£π€£π€£
"IT WORKS ON MY MACHINE"
(although I see a container right there π)
Containerization fixes everything!
Only if it's in the container