[ https://issues.apache.org/jira/browse/SPARK-4159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14273062#comment-14273062 ]
Apache Spark commented on SPARK-4159: ------------------------------------- User 'srowen' has created a pull request for this issue: https://github.com/apache/spark/pull/3993 > Maven build doesn't run JUnit test suites > ----------------------------------------- > > Key: SPARK-4159 > URL: https://issues.apache.org/jira/browse/SPARK-4159 > Project: Spark > Issue Type: Bug > Components: Build > Reporter: Patrick Wendell > Assignee: Sean Owen > Priority: Critical > Labels: backport-needed > Fix For: 1.3.0 > > > It turns out our Maven build isn't running any Java test suites, and likely > hasn't ever. > After some fishing I believe the following is the issue. We use scalatest [1] > in our maven build which, by default can't automatically detect JUnit tests. > Scalatest will allow you to enumerate a list of suites via "JUnitClasses", > but I cant' find a way for it to auto-detect all JUnit tests. It turns out > this works in SBT because of our use of the junit-interface[2] which does > this for you. > An okay fix for this might be to simply enable the normal (surefire) maven > tests in addition to our scalatest in the maven build. The only thing to > watch out for is that they don't overlap in some way. We'd also have to copy > over environment variables, memory settings, etc to that plugin. > [1] http://www.scalatest.org/user_guide/using_the_scalatest_maven_plugin > [2] https://github.com/sbt/junit-interface -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org For additional commands, e-mail: issues-h...@spark.apache.org