Our frontend tests with Jasmine used to take 40 minutes to run. It was ridiculous, so I looked at it, read some docs, and reduced it to 1 minute a 30 seconds.
How long is too long? I would say that depends on how fast your team is working, and what your budget is. For us, iterating faster on features and bug fixes is the right quality we want to deliver. Waiting for tests to finish can get expensive quick, especially if your team is blocked from merging code.
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.
Our frontend tests with Jasmine used to take 40 minutes to run. It was ridiculous, so I looked at it, read some docs, and reduced it to 1 minute a 30 seconds.
The problem was not isolating modules for a test:
github.com/kulshekhar/ts-jest/blob...
How long is too long? I would say that depends on how fast your team is working, and what your budget is. For us, iterating faster on features and bug fixes is the right quality we want to deliver. Waiting for tests to finish can get expensive quick, especially if your team is blocked from merging code.
Hey! That's a serious change in pace!