News for hackers. Stuff that matters.
Re:Stop requiring only one assertion per unit test: Multiple... by hinkley on Sunday November 06, 2022 @05:33AM (#33491148)
Never disable the timeouts. What you want is a way to set the timeouts once for an entire suite. Unit, functional, and integration tests all have a different threshold from each other. But in general within one kind your outliers almost always have something wrong with them. They’re either written wrong or the code is. And once I’m a while it’s okay to override the timeout on one test while you’re busy working on something else.

The problems isn’t with breaking rules. The problem is with promising yourself or others that you will fix it “later” and then breaking that promise.

There are no comments on this comment yet.