incubator-crunch-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tom White (JIRA)" <>
Subject [jira] [Commented] (CRUNCH-17) Split unit tests from integration tests
Date Wed, 18 Jul 2012 14:56:33 GMT


Tom White commented on CRUNCH-17:

> I would *really* like it if the full test suite would run more quickly, but that's another
story (which might involve using the MemPipeline a lot more in the automated tests). 

I was thinking that this could be done by parameterizing the test suite so that you could
run the tests i) in-memory, ii) using MR-pipeline, or iii) both. This would be controllable
via a command line switch (e.g. a system property), and could be implemented using
> Split unit tests from integration tests
> ---------------------------------------
>                 Key: CRUNCH-17
>                 URL:
>             Project: Crunch
>          Issue Type: Task
>          Components: Core
>            Reporter: Matthias Friedrich
>            Assignee: Matthias Friedrich
>              Labels: maven
>             Fix For: 0.3.0
>         Attachments: 0001-CRUNCH-17-Split-unit-from-integration-tests.patch.gz, 0002-CRUNCH-17-Scrunch-test-reorganization.patch.gz
> 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:!default.jspa
For more information on JIRA, see:


View raw message