search

FRosner / DataGenerator

Tool for generating various test data for machine learning and data mining algorithms.
Apache License 2.0
10 stars 2 forks source link

Execute long running UI tests in separate test phase #156

Closed FRosner closed 11 years ago

FRosner commented 11 years ago

The UI tests are growing and it would be nice to exclude them from the test phase and execute them in a separate test phase.

FRosner commented 11 years ago

http://stackoverflow.com/questions/3100924/how-to-run-junit-tests-by-category-in-maven tells me to use profiles for this. I should have a default profile that executes no long running tests and a profile that executes all tests.

FRosner commented 11 years ago

Phases are pretty hard core. I introduced a profile to exclude long running UI tests. If we ever get a build server we can exclude them by default and have the profile include them for daily use.

FRosner commented 11 years ago

@Husterknupp you may now exclude the long running GUI tests by executing mvn <phase> -P no-gui, where <phase> is one of the phases including test (that is test or package for now).

But I highly recommend not to exclude the GUI tests all the time. It can be nice if you want to check a single commit but before pushing a lot of changes please execute all the tests: mvn test.

When we have a build server we could discuss to switch the standard behaviour in a way that does not execute long running tests and leave them for the nightly build. Until then we will have to execute them on our machine before building.