[
https://issues.apache.org/jira/browse/SPARK-2712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14078551#comment-14078551
]
Sean Owen commented on SPARK-2712:
----------------------------------
Yes, exactly so. Maven runs test, then package, then integration-test.
Integration tests are supposed to be the things that require things like
packaging.
The ideal practice is to name unit tests (i.e. stand-alone tests that don't do
anything long or complex) have a certain naming convention and integration
tests have another, and then it's pretty simple mojo to bring in the failsafe
plugin to manage integration tests. Then this just works. Really that part is
easy as pie.
The hard part would be separating out and renaming unit tests. I'd even
volunteer for that if there was some clear support for it.
> Add a small note that mvn "package" must happen before "test"
> -------------------------------------------------------------
>
> Key: SPARK-2712
> URL: https://issues.apache.org/jira/browse/SPARK-2712
> Project: Spark
> Issue Type: Documentation
> Components: Documentation
> Affects Versions: 0.9.1, 1.0.0, 1.1.1
> Environment: all
> Reporter: Stephen Boesch
> Priority: Trivial
> Labels: documentation
> Fix For: 1.1.0
>
> Original Estimate: 0h
> Remaining Estimate: 0h
>
> Add to the building-with-maven.md:
> Requirement: build packages before running tests
> Tests must be run AFTER the "package" target has already been executed. The
> following is an example of a correct (build, test) sequence:
> mvn -Pyarn -Phadoop-2.3 -DskipTests -Phive clean package
> mvn -Pyarn -Phadoop-2.3 -Phive test
> BTW Reynold Xin requested this tiny doc improvement.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
