You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since we introduced mutation testing I've noticed that the build time has increased significantly compared to the few minutes it took previously to now run in about 25 minutes.
Is there a way we can improve the time the mutation tests take to run? I've not used it myself before, so I'm not familiar with whether or not ~20 minutes to run the tests for a codebase the size of Polly's is expected/normal.
If it's just a fact of life with the use of this approach that's fine, but if there's something we can do to speed it up that would be good.
The text was updated successfully, but these errors were encountered:
@martincostello
The mutation testing takes a long time. In our code-base we have some tricks to only run mutation tests on affected projects (otherwise our runs could take > 5 hours).
The problem is that infrastructure is internal and would be hard to replicate here. There are plans to make it public so we can use it once it's available.
Since we introduced mutation testing I've noticed that the build time has increased significantly compared to the few minutes it took previously to now run in about 25 minutes.
Is there a way we can improve the time the mutation tests take to run? I've not used it myself before, so I'm not familiar with whether or not ~20 minutes to run the tests for a codebase the size of Polly's is expected/normal.
If it's just a fact of life with the use of this approach that's fine, but if there's something we can do to speed it up that would be good.
The text was updated successfully, but these errors were encountered: