You must log in or register to comment.
At my work, we have a big Rails app with lots of tests
Of course they need a blog post to get test times down to something that’s already way too slow. Ruby and Rails are such a dumpster fires
Not a fan of Ruby, but the things they outline here are pretty good for testing just about any language.
I maintain a fork of llvm and a JIT runtime written in Rust where we’ve employed some of these same techniques. E.g. caching llvm builds, running things in parallel…
Any sufficiently complex, well tested, system has the potential for long CI times. It’s not something unique to Ruby or dynamic languages.