521

Inm looking at you Typescript dev (sh.itjust.works)

submitted 1 year ago by Wats0ns@sh.itjust.works to c/programmer_humor@programming.dev

50 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[-] jubilationtcornpone@sh.itjust.works 17 points 1 year ago

Must be the same people who just comment out failing unit tests.

[-] OsrsNeedsF2P@lemmy.ml 6 points 1 year ago

"Your crappy tests are failing again on my branch. I've commented them out until you fix them."

[-] Hudell@lemmy.dbzer0.com 2 points 1 year ago

Sadly that sort of thing got so common where I work that I'll run the tests three times before considering looking into the error message to see if it is something I broke.

From time to time we take some days just to fix tests with inconsistent results, but there's always more popping up.

[-] Darorad@lemmy.world 1 points 1 year ago

Yeah, we have a team whose job is to make sure all our tests run well and fixing them if they don't

[-] OsrsNeedsF2P@lemmy.ml -1 points 1 year ago

Serious answer: You can't write tests for untestable code. Your code needs to be pure if you want reliable tests: https://en.m.wikipedia.org/wiki/Pure_function

For integration tests, they should handle retries themselves