2 unit tests. 0 integration tests.

Ben Halpern 🦁

@bendhalpern

2 unit tests. 0 integration tests.

12:21 PM - 09 Nov 2019

23 85

Comments

[Yaser Al-Najjar]

"IT WORKS ON MY MACHINE"
(although I see a container right there 😁)

[Matt Eland]

Containerization fixes everything!

[Benjamin Davies]

Only if it's in the container

[Balaji K]

Clear cache and try again 😉

[MOHAMMEDALI]

🤣🤣🤣🤣

[Victor Yarema]

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".

[Anh Tu Nguyen]

Depend on described use cases, this is undocumented user behavior!

[Zohar Peled]

Users. If we could only do without them, what a wonderful world it could be :-)

[katy lavallee]

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.

[Yene]

Expected behaviour

[Uchendu Precious]

Just handle exceptions properly.

[Ali GOREN]

Use CTRL+R

[David J Eddy]

This is great!

[Marino Poletine]

Why,docker, why???

[testing.tips]

Don't trust the user, add validation.

[cloudwolf]

2 unit tests and 1 integration test but needed a 2nd with the input order flipped

[MOHAMMEDALI]

Input fail due errors is vswr