Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 2.7.1
-
Fix Version/s: 2.7.2
-
Component/s: TestNG support
-
Labels:None
-
Environment:ubunut
-
Complexity:Intermediate
-
Number of attachments :
Description
I have a project which contains Unit Tests in relationship with TestNG (5.14.6) and the maven surefire plugin (2.7.1) which produces the following output:
[INFO] --- maven-compiler-plugin:2.3.2:testCompile (default-testCompile) @ sapm --- [INFO] Compiling 15 source files to /home/kama/ws-git/sapm/target/test-classes [INFO] [INFO] --- maven-surefire-plugin:2.7.1:test (default-test) @ sapm --- [INFO] Surefire report directory: /home/kama/ws-git/sapm/target/surefire-reports ------------------------------------------------------- T E S T S ------------------------------------------------------- Running TestSuite Running TestSuite Tests run: 225, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.332 sec Results : Tests run: 225, Failures: 0, Errors: 0, Skipped: 0 [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESS [INFO] ------------------------------------------------------------------------ [INFO] Total time: 7.053s [INFO] Finished at: Mon Jan 03 10:31:32 CET 2011 [INFO] Final Memory: 22M/147M [INFO] ------------------------------------------------------------------------
There you can see the doubled "Running TestSuite". I have checked that against maven-surefire plugin (version 2.6) which produces the same output except the double "Running TestSuite".
Issue Links
- is related to
-
SUREFIRE-679
[regression] TestNG suite no longer succeeds, with error "testSetStarting called twice"
-