3 ms·

i think it usually boils down to "its tests, its not performance sensitive" then tests take 10x the build time and eventually impact productivity like crazy :(

• tajen 11y ago
  At my startup (35 devs on the main product), we'd spin off a dozen AWS instances so the tests would run in 20 minutes in parallel. And only tested commits could be merged into master. We didn't feel it as a bad situation.
  • nulltype 11y ago
    It seems like renting computers by the minute is pretty cheap these days. I'm surprised more people don't just have one machine per test, run them all in parallel. Testing seems to be embarrassingly parallel in that usually your tests don't depend on other tests at all.
    • zobzu 11y ago
      most of the problem is when tests depend on each other, which they oftentimes do or when they shouldnt but do, theres a large amount of work to change that
    • tajen 11y ago
      Unit tests are short, but integration tests require the app to start and setup, which takes around 3 minutes. Then each test is quite independent.