I try to keep it down to 15 minutes (including end to end) because any longer than that and people start complaining. If you've already optimized your tests consider running multiple builds concurrently.
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.
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.
I try to keep it down to 15 minutes (including end to end) because any longer than that and people start complaining. If you've already optimized your tests consider running multiple builds concurrently.
Yeah, I think 15 minutes is a good timeframe. Do you run multiple builds concurrently now?
I implemented it on some projects in the past, yes. If I didn't the CI run would've probably lasted 50+min.
Yep. I’ve worked at places with where an entire run is between 2 and 3 hours without running test concurrently.