[
https://issues.apache.org/jira/browse/CRUNCH-17?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13413512#comment-13413512
]
Matthias Friedrich commented on CRUNCH-17:
------------------------------------------
Most developers I've worked with run the entire test suite from the IDE and
only use Maven once before they commit. I've seen people from the TDD crowd run
the test suite every couple of minutes. Some also like up to the minute
accurate test coverage reports via EclEmma.
In my opinion, right now the test suite is a hurdle for new contributors. Just
being able to run the examples requires running the test suite (unless you know
the right Maven switch) and that takes 25 minutes (!) on my office machine. On
my home notebook (centrino 2, but with a slow disk) I guess it would be a lot
longer if it actually succeeded. Like with Hadoop, you can't contribute unless
you've got a fast developer workstation available.
So, what do you want me to do? I could start without the separate Maven module
and then we re-evaluate?
> 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
