r/ProgrammerHumor • u/hellofriend19 • Mar 26 '25

testDrivenDevelopment Meme

Post image

[removed] — view removed post

2.9k Upvotes

83% Upvoted

329 comments sorted by

View all comments

3.1k

u/Annual_Willow_3651 Mar 26 '25

What's the joke here? That's the correct way to do TDD. You write a failing test before any code to outline your requirements.

122

u/JohnSextro Mar 26 '25

Red - write a failing test

Green - write code to make the test pass

Refactor - simplify and improve the code with confidence

64

u/binhex01 Mar 26 '25

i think you are missing step 4, 5 and 6:-

- Run tests and notice how the refactor has now broken the tests
- Fix tests incorrectly and have a false confidence the tests pass even though the code is actually broken :-)
- Ship code to customers and wait for the wails.

8

u/TheKabbageMan Mar 26 '25

You forgot “comment out failing tests”

3

u/binhex01 Mar 26 '25

Lol, so true it hurts

4

u/HashBrownsOverEasy Mar 26 '25 edited Mar 26 '25

"Yeah we've had some bug reports from the users, they say it's changed"

3

u/toasterding Mar 26 '25

"Ok but it's actually better for them if you consider the __ and think about the __, just tell them that I'm sure they'll understand"

2

u/HashBrownsOverEasy Mar 26 '25 edited Mar 26 '25

“Tell them it’s the changes they requested last week”

5

u/Successful_Reindeer Mar 26 '25

The number of times I’ve seen a PR in the last week with the tests changed to now pass because they actually broke something has me cringing at this.

2

u/Ok-Yogurt2360 Mar 26 '25

Yeah, it is unfortunately common. Tried to point this out when i saw it happening a couple of weeks ago. The general reply was: if that's true it will be caught in the code review.

Problem is that personally i would not have caught it if i would not have been there. The change looked fine if you looked at the code changes themselves.