5 ms·
This part is good: https://abseil.io/resources/swe-book/html/ch13.html#prefer_realism_over_isolation https://abseil.io/resources/swe-book/html/ch13.html#prefer_
by dboreham 3y ago
This part is good: https://abseil.io/resources/swe-book/html/ch13.html#prefer_realism_over_isolation https://abseil.io/resources/swe-book/html/ch13.html#prefer_r...
- kyrra 3y agoI'd say it's a tradeoff. If you are entirely driven by tests that include your deps, they will be slow. Unit tests are good at catching basic behavior issues that would show up with an integration test, but it's easier to see the cause. I'm of the opinion that both are needed, but don't put all your eggs in unit tests (they don't need to be perfect). That extra time being spent on integration tests tend to be better for maintaining system health.
- compiler-guy 3y agoGoogle's massive distributed build system also runs tests and so most projects run their dependent tests in parallel on thousands of machines.
- kuchenbecker 3y agoWith an optional --runs-per-test=1000