[
https://issues.apache.org/jira/browse/CRUNCH-17?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13413085#comment-13413085
]
Matthias Friedrich commented on CRUNCH-17:
------------------------------------------
After some research it seems there's still no perfect solution with
Maven/JUnit/Eclipse. Just renaming the slow tests from *Test to *IT and using
the Maven Failsafe Plugin to execute them during the integration-test phase
isn't enough. You'd still need a way to keep them apart in the IDE without
having to build test suites manually. I'm leaning towards the solution we use
at work: Move the integration tests out of the way into a separate Maven
module, rename them and run them via the Failsafe Plugin.
Thoughts?
> Split unit tests from integration tests
> ---------------------------------------
>
> Key: CRUNCH-17
> URL: https://issues.apache.org/jira/browse/CRUNCH-17
> Project: Crunch
> Issue Type: Task
> Components: Core
> Reporter: Matthias Friedrich
> Assignee: Matthias Friedrich
> Labels: maven
>
> Currently, the test suite is a mix of fast unit tests and slow integration
> tests which prevents developers from executing tests early and often. It
> should be possible to run unit tests separately via Eclipse (or some other
> IDE) and Maven. Integration tests should run in Maven's integration-test
> phase.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
