Filter unit tests files listed in surefire reports

Peter Niederwieser added a comment - 19/Aug/11 10:53 AM Would it be possible to include non-Java tests in Sonar test statistics even if Sonar can't analyze their source code? This would go a long way towards supporting non-Java tests, which is becoming a popular practice in today's Java projects. For example, Gradle has thousands of Groovy tests, and many of our customers also use Groovy for testing.

Freddy Mallet added a comment - 23/Aug/11 8:20 AM Hi Peter, I guess you're talking about the Sonar Groovy plugin whereas this ticket was focused on java projects containing some groovy tests which have to be ignored ?

Peter Niederwieser added a comment - 23/Aug/11 6:10 PM No, I'm also talking about the case where a Java project has tests written in another language (say Groovy). Ignoring these tests isn't a good solution. (To give an example, for the Gradle project it would mean that about half of our 4000+ tests wouldn't show up in Sonar.) Therefore I asked whether Sonar could, as an interim solution until it supports multiple languages per project, make use of the information in test result XML files even if it can't correlate that information with any source code.

Felix Müller added a comment - 06/Jun/12 4:10 PM Hi, I'm also facing this problem with a bunch of unit tests written in Groovy in a Java project. Could you think about a workaround until full multi-language support is available (I think this will last a few versions?). Cheers, Felix

Freddy Mallet added a comment - 06/Jun/12 4:24 PM Hi Felix, but We don't know how to fix this issue without fixing first SONAR-926 .

Andrew Logvinov added a comment - 18/Oct/12 4:50 AM I came across this ticket in search of an answer for the question whether Sonar takes into account groovy tests when counting test coverage. The answer seemed to be "no", but then I remembered that we actually had one test in groovy in our project. And I was surprised to see, that it was counted in code coverage calculation. So I decided to share our configuration since it might be useful for someone. We have a multi-module maven project and to be able to use groovy unit tests, we have declared the following dependency: <dependency> <groupId>org.codehaus.groovy</groupId> <artifactId>groovy-all</artifactId> <version>1.8.6</version> <scope>test</scope> </dependency> And this has to go to build --> plugins section: <plugin> <groupId>org.codehaus.gmaven</groupId> <artifactId>gmaven-plugin</artifactId> <version>1.4</version> <dependencies> <dependency> <groupId>org.codehaus.gmaven.runtime</groupId> <artifactId>gmaven-runtime-1.8</artifactId> <version>1.4</version> <exclusions> <exclusion> <groupId>org.codehaus.groovy</groupId> <artifactId>groovy-all</artifactId> </exclusion> </exclusions> </dependency> <dependency> <groupId>org.codehaus.groovy</groupId> <artifactId>groovy-all</artifactId> <version>1.8.6</version> </dependency> </dependencies> <executions> <execution> <id>compile-groovy</id> <phase>process-test-sources</phase> <goals> <goal>testCompile</goal> </goals> <configuration> <providerSelection>1.8</providerSelection> <verbose>true</verbose> <sources> <fileset> <directory>${project.basedir}/src/test/groovy</directory> <includes> <include>**/*.groovy</include> </includes> </fileset> </sources> </configuration> </execution> </executions> </plugin>