Hacker News new | past | comments | ask | show | jobs | submit login

> You keep a count and any time a test fails/recovers 3 times it gets skipped, even if there's weeks between failures.

Congratulations, you now have an untested feature.

Flaky tests should be fixed, of course. But just deleting them isn't fixing them, and it leaves you worse off, not better.

May i ask how you feel about TODO comments?




If you re-read my comment you'll see I already addressed this. Not having a test is better than having a flaky test.

The team should feel the pain of having their shit test skipped without them being able to stop it and it's up to them to either fix it and bring it back or cope.


> Not having a test is better than having a flaky test.

What i'm saying is that you are completely wrong about that. Sorry if i wasn't clear.


Ok that's more clear, this is fine then we know we disagree (also why i called it a bit of a religion). Have a great day!

PS: if the test was flaky, you already had an untested feature




Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: