Running both scalatest tests and junit tests with maven plugin

[pe...@vagaband.co]

I have an existing project that has both junit tests and newer scalatests within a maven project. I'm using scalatest-maven-plugin but it seems to only run scalatests and not junit tests. Is there a way to get it to run both type of tests? If I added <junitClasses> field, it will run junit tests but will skip scalatests. I want to run both and preferably not have to list every test class in the pom. Is there a way to do this?

Thanks,

Peter

[Bill Venners]

Hi Peter,

Sorry, Google groups decided your email was likely spam, and didn't notify me that it was sitting there until today. Hopefully you figured out a solution already, but the lowdown is:

If a jUnitClasses element is specified in the pom, the scalatest-maven-plugin just adds those specified classes as -j options in the argument list passed to Runner.  It doesn't affect how any other arguments are processed.

But if classes are specified like that then Runner treats them as a list of suites to run, and doesn't do any further discovery, so unless some scalatest suites are specified, either individually or using membersOnlySuites or wildcardSuites or globs, then only the junit classes will get run.

More details here:

http://scalatest.org/user_guide/using_the_scalatest_maven_plugin

Let me know if that solves the problem. 

Thanks.

Bill

--
You received this message because you are subscribed to the Google
Groups "scalatest-users" group.
To post to this group, send email to scalate...@googlegroups.com
To unsubscribe from this group, send email to
scalatest-use...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/scalatest-users?hl=en
ScalaTest itself, and documentation, is available here:
http://www.artima.com/scalatest
---
You received this message because you are subscribed to the Google Groups "scalatest-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to scalatest-use...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

--
Bill Venners
Artima, Inc.
http://www.artima.com

[pe...@vagaband.co]

Hi Bill,

Actually I have not been able to figure it out. I must be missing something very simple. I was just experimenting with junitClasses option to see whether it helps but like you said that's not intended for what I'm looking for.

I'm looking to run both scalatest/junit tests without having to specify individual tests in the pom. I have the pom configured like this ->

            <plugin>

                <groupId>org.scalatest</groupId>

                <artifactId>scalatest-maven-plugin</artifactId>

                <version>1.0-RC1</version>

                <configuration>

                    <reportsDirectory>${project.build.directory}/surefire-reports</reportsDirectory>

                    <junitxml>.</junitxml>

                    <filereports>WDF TestSuite.txt</filereports>

                </configuration>

                <executions>

                    <execution>

                        <id>test</id>

                        <phase>test</phase>

                        <goals>

                            <goal>test</goal>

                        </goals>

                        <configuration>

                            <parallel>true</parallel>

                            <tagsToExclude>Integration-Test</tagsToExclude>

                        </configuration>

                    </execution>

                    <execution>

                        <id>integration-test</id>

                        <phase>integration-test</phase>

                        <goals>

                            <goal>test</goal>

                        </goals>

                        <configuration>

                            <parallel>false</parallel>

                            <tagsToInclude>Integration-Test</tagsToInclude>

                            <systemProperties>

                                <integration.test.host>${integration.test.host}</integration.test.host>

                                <integration.test.port>${integration.test.port}</integration.test.port>

                            </systemProperties>

                        </configuration>

                    </execution>

                </executions>

            </plugin>

And I have regular junit tests under src/test/java and scalatests under src/test/scala. With this it's only picking up scalatests. Is there something additional I need to do to also pick up the junit tests from src/test/java?

Thanks,

Peter

PS - ScalaTest is the only tool that restored my faith in testing frameworks... it's a joy to work with.

[Bill Venners]

Hi Peter,

ScalaTest doesn't currently discover JUnit tests. You have to explicitly name them. We are looking into how Surefire discovers JUnit tests. I'm guessing they look for @Test, etc., annotations, but we'll investigate. In the meantime, I wonder if you can use Surefire to discover and run the JUnit ones and ScalaTest to discover and run the ScalaTest ones. The other thing to try is to see if JUnit has a programmatic way (some API) to discover JUnit tests and wrap that in a Suite that you explicitly ask the ScalaTest Maven Plugin to run. I'll keep you posted on what we find out. Let me know if you discover anything in the meantime.

Bill

[Matthew Farwell]

Just for information, JUnit itself doesn't do discovery of JUnit tests. The heart of Maven Surefire is https://github.com/apache/maven-surefire/blob/master/maven-surefire-common/src/main/java/org/apache/maven/plugin/surefire/util/DirectoryScanner.java.

There is a library called ClasspathSuite which allows you to create a Suite which scans the classpath: http://johanneslink.net/projects/cpsuite.jsp

Have fun,

Matthew Farwell.

[Bill Venners]

Hi Matthew,

Thanks! That helps.

Bill

[Eugene Platonov]

Hi Bill,

is there any progress on this matter?

~

Best Regards,

Eugene

[Bill Venners]

Hi Eugene,

We implemented a solution, but I didn't merge it in because I felt it was the wrong way to do it.  I am on a phone right now so can't easily point you to it,  but if you go look at the pull requests for scalatest on github you should see it.  It does discovery of all JUnit tests On the classpath if you specify -J on the command line. I think it may be better to have -J mean include also discover JUnit tests based on the-s, -m, -w params so you can be more precise about what runs. But I also wasn't sure that might be to course grained,  so we haven't fine further.  If so, though, i Was not sure how best to incorporate that into the command line.  What would you (and others with am interest) ideally want?

Bill

For more options, visit https://groups.google.com/d/optout.

[Marcelo Turrin]

Hello,

I'm having a similar necessity and as I think this have not been move forward since the last post let me see if I can at least tell my case that I assume could be common.

My team has been developing a java application for the last 3 years, is a distributed chain of web rest services that make a product. Without going to much into it is just a lot of moving parts (with java, groovy, storm, elastic search, etc).

We wanna start moving towards developing in scala, but as we have a lot done and to start easying our way in we decided to start coding test to get the hang of the language.

Now we are trying to integrate it and what it is stopping us to move forward is that we cannot run our old test in Java (and Groovy) via maven if we add scala test (as it requires to disable surefire).

And adding each test to the pom is not an option as we have hundreds and modifying the pom each time we need to add a test is not practical.

So the necessity is simply put is that we run mvn clean install we need this command to discover (as surefire doues) and run all test: scala, java and groovy so our developers and specially our continues integration scheme can create test in scala without loosing what they already have.

I know that perhaps this is not one of the priorities for your project so I wanted to ask if  this was on your roadmap or you think it will be or if you have an alternative I could have missed to finally be able to come up with a decisson on how to move forward with this scala integration posibility.

Thank you very much 

[Łukasz Sanek]

Hi,
I've had a similar problem and I solved it by simply running both JUnit and ScalaTest tests with maven-surefire-plugin (the scalatest-maven-plugin is not needed). You can have a look at the sample Maven project here: https://github.com/s4nk/scalatest-maven-template

Lukasz

[Juancho J]

Hi Lukasz,

I have followed the pattern you reference. The java tests still run. However, the scala ones don't. Here's the snippet of my pom:

<plugin>

 <groupId>org.apache.maven.plugins</groupId>

 <artifactId>maven-surefire-plugin</artifactId>

 <version>2.16</version>

 <configuration>

 <threadCount>5</threadCount>

 <parallel>classes</parallel>

 <reportsDirectory>target/testng-surefire-reports/</reportsDirectory>

 <excludedGroups>cleanup</excludedGroups>

 <includes>

         <include>**/*Spec.*</include>

 </includes>

 </configuration>

 </plugin>

 <plugin>

 <groupId>net.alchim31.maven</groupId>

 <artifactId>scala-maven-plugin</artifactId>

 <executions>

                     <execution>

                         <id>scala-test-compile</id>

                         <phase>process-test-resources</phase>

                         <goals>

                             <goal>add-source</goal>

                             <goal>testCompile</goal>

                         </goals>

                     </execution>

                    </executions>

 </plugin>

Could you possibly help me w/ this?