Testing
Post #4242 · source on Telegram
Actual Code, Imaginary Unit Tests
Description
The image is a comic-style two-column comparison labeled "ACTUAL CODE" on the left and "UNIT TESTS" on the right. The left panel shows a tall editor-like area filled with colored horizontal bars representing many lines of source code, while the right panel is an equally large empty gray box. A watermark at the bottom reads "@THEJENKINSCOMIC" and there is also a partial "t.me/dev_meme" mark. The technical humor is the all-too-common imbalance between production code and the nonexistent tests that are supposed to protect it.
Use J and K for navigation
Comments
16Comment deleted
The coverage report is impressively fast when the test suite is just an empty directory with confidence issues.
Definitely Comment deleted
The question is, where are unit tests for unit tests? Comment deleted
🧠 Comment deleted
Damn man, that's the best query i've ever seen! Comment deleted
Unit test should represent simple operation which is not needed to be tested (Короче говоря если вы считаете что юнит тесты нуждаются в тестах, то вы не понимаете смысл юнит тестов (с) какая то статья на хабре) Comment deleted
Add fixtures and world falls apart in 'em Comment deleted
I'm in this picture and I dont like it. Comment deleted
What if I have unit tests, but not run them? Comment deleted
It is life 😐 (жиза) Comment deleted
not life (не жиза) Comment deleted
You are lucky man (Везёт) Comment deleted
s/lucky/fucking lazy/ Comment deleted
better empty both sides Comment deleted
😂😂😂😂 Comment deleted
Fassbender: "Perfection" Comment deleted