Details
-
Bug
-
Resolution: Not a bug
-
Low
-
4.0.1
-
None
Description
I am validating if our company can you clover to reduce the test run time using the test optimize feature. For demonstration purpose i created a sample maven project. It has 4 APIs.
1. Add
2. Subtract
3. Multiply
4. MultiplyVersion2
My scenario is DEVELOPER makes a codechange and checks it in. junit testing API no 4 fails. Clover intelligent enough to run the junit that tests MultiplyVersion2. As the JUNIT fails component is broken and build fails. Developer detects he caused a regression and fixes the issue. I notice that clover doesn't add any tests once developer fixes the issue. . As per my understanding there should be latest one JUNIT(the one that failed last time) run. Our CI system didnt run any tests after the fix. So there were no JUNIT result reports. So the build was marked as broken though it actually fixed by the developer. It shouldn't work this way right?
Attached sample project for your reference.
Here is the maven goal I used in jenkins
clover2:setup clover2:optimize test clover2:snapshot -e -Dmaven.test.failure.ignore=false
Here is the clover log :-
[INFO] Clover estimates having saved around 6 seconds on this optimized test run. The full test run takes approx. 6 seconds
[INFO] Clover included 0 test classes in this run (total # test classes : 3)
Notice that no tests are added.