-
Improvement
-
Resolution: Won't Fix
-
Major
-
None
-
v1.25
We'd like to enforce that our code coverage always be rising (basically any new code should have unit tests). That requires us to constantly re-configure our builds to up the code coverage thresholds (plus there's currently no way to mark a build failed/unstable due to coverage being too low).
If the current build's coverage numbers go down since the last stable build, this build should get marked unstable.