DEV Community

Discussion on: How long does it take for your test suite to run?

Collapse
drews256 profile image
Andrew Stuntz Author

For sure! Are you guys optimizing but increasing server costs? A lot of the solutions I have used in the past have all been parallelizing tests across multiple machines.

Collapse
_garybell profile image
Gary Bell

No. Our unit tests run on GitLab so there's no additional cost to us.

Basicslly instead of running all tests a-z, we split them into batches where each one takes 6-8 minutes.

Whilst it may use a few more pipeline minutes, I'm not as worried about that as I would be having a developer sat round doing nothing for 30 minutes

Thread Thread
drews256 profile image
Andrew Stuntz Author

Oh this is totally my point. I’ve worked at a few places where they refuse to increase the infrastructure for testing “cause it’s too expensive” but there devs would spend 2 or 3 hours a day waiting for tests to run. It’s just a wild culture and poor understanding by management and poor ownership by the dev team.

Thread Thread
_garybell profile image
Gary Bell

I work in a brilliant place where they understand the cost of having people sat round waiting for half a day.

We will get to a point where the runners for the pipeline are in our infrastructure, and if they are slow we can throw more resource at them. Or each developer can have their own dedicated runner. It won't cost a lot, and free up a lot of time.

All stuff for next year!