Timeline for How do we make unit tests run fast?
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 21, 2022 at 6:01 | comment | added | kiwicomb123 | Can't agree more! Someone tried to convince me that doing all development in Virtual Machines would be a good route to go. But unit tests ran 400% SLOWER in the VM,. making it so that we spent more time sitting there waiting to get feedback on code, rather than actually coding. | |
| Aug 22, 2018 at 20:54 | comment | added | fourpastmidnight | And how can you possibly not agree with #5?!? in addition to 1 & 3, or heck, 2 & 4, too! Anyway, great answer all around. | |
| Sep 7, 2014 at 19:29 | comment | added | Bill IV | STRONGLY agree, particularly point 3 & 1. If developers aren't running tests, then the tests are broken, the environment is broken, or both. Point 1 is the minimum. False fails are worse than missing tests. Because people learn to accept fails. Once failure is tolerated, it spreads, and it takes a mighty effort to get back to 100% passing and EXPECTING 100% passing. Start fixing this today. | |
| Jan 26, 2013 at 19:53 | history | answered | Jay Bazuzi | CC BY-SA 3.0 |