4 ms·
As much as the author calls themself out in the subtitle, they do lead with the actual "TLDR". > It’s called TLDR and it blows up if your tests take more than
by lcnPylGDnU4H9OF 3y ago
As much as the author calls themself out in the subtitle, they do lead with the actual "TLDR".
> It’s called TLDR and it blows up if your tests take more than 1.8 seconds to run.
> The big idea is to run as much of your test suite as you can as often as you can, as opposed to only running whatever test you’re actively working on and saving the full test suite for CI.
The stated objective sounds nice. I have no idea how sensible or thought-out the 1.8 seconds decision is but keeping the whole suite at less than 2 seconds "feels right" as it were, especially in a CI/CD context. Probably most valuable is setting some timeout and ideally setting it as low as possible.