I'm a full stack developer working on building web applications for all sorts of sized companies using a wide variety of web technologies. Mostly working in Ruby and JavaScript.
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.
A Senior Developer working mostly with PHP and JavaScript, with a bit of Python thrown in for good measure, all on Linux. My tooling is simple, it's GitLab and JetBrains where possible.
I'm a full stack developer working on building web applications for all sorts of sized companies using a wide variety of web technologies. Mostly working in Ruby and JavaScript.
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.
A Senior Developer working mostly with PHP and JavaScript, with a bit of Python thrown in for good measure, all on Linux. My tooling is simple, it's GitLab and JetBrains where possible.
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!
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
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.
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
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.
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!