Hi,
Jeanfrancois Arcand wrote:
> Salut,
>
> Oleksiy Stashok wrote:
>> Hi,
>>
>> wanted to ask.
>> It's only me, who thinks, that running all unit test set on each
>> build, it's something undesirable? :))
>> For example I would like to add unit tests for
>> Controller/SelectorHandler pause/resume operations. But they will
>> include tests, which should fail by timeout, for example when
>> SelectorHandler is paused - client will end with timeout when trying
>> to receive response...
>> I can commit that tests, but it will mean total test execution time
>> will be increased by approx. 30sec - 1min or may be more.
>
> Commit it. There is a property called:
>
> -Dmaven.test.skip=true
>
> that allow not running the test.
It means tests will not be run on each building, but still, if I need -
I can run them?
> If we can start pushing Hudson results to this alias instead of our
> private one, I would say we can start using the property (carefully).
I agree. But first, IMHO, we should move Hudson public, so it will make
sense to send mails here.
Thank you!
WBR,
Alexey.
>
> Thanks
>
> -- jeanfrancois
>
>
>>
>> I'm not maven guru, so would like to ask, if there any common
>> practices, which may be other projects use, that will allow us to run
>> unit tests, when we really need that, but not on each build?
>>
>> Thanks.
>>
>> WBR,
>> Alexey.
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe_at_grizzly.dev.java.net
>> For additional commands, e-mail: dev-help_at_grizzly.dev.java.net
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_grizzly.dev.java.net
> For additional commands, e-mail: dev-help_at_grizzly.dev.java.net
>