You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@abdera.apache.org by Adam Constabaris <ad...@clownsinmycoffee.net> on 2007/02/24 23:58:43 UTC

Re: [jira] Updated: (ABDERA-39) Selectively disable unit tests that depend on external services

> Rather than disable those tests, I'd much rather that we develop some
> equivalent tests that we can add to our svn.  Those particular tests
> help us to verify some rather important Atom conformance features.

Agreed on both counts.  I generated the patch yesterday morning when my
workstation couldn't get any response back from verisignlabs.  My
immediate options were no build at all, a completely untested one, or a
partially tested one.  

Further commentary: the patch doesn't disable the tests full stop -- it
adds a  profile which has to be specifically enabled on the command line
(e.g. mvn -P no-online-tests clean install); without the special
incantation, all tests will still be run.  An alternate approach is to
add the profile to one's local settings.xml.

cheers,

AC




Re: [jira] Updated: (ABDERA-39) Selectively disable unit tests that depend on external services

Posted by James M Snell <ja...@gmail.com>.
fyi.. unless one of the other committers gets to it first, I'll look to
apply this patch and fix up the tests by this weekend.  I'll also be
looking at the documentation you contributed.

Thank you very much, btw.  It's great to see a user contributing back to
the project.

- James

Adam Constabaris wrote:
>> Rather than disable those tests, I'd much rather that we develop some
>> equivalent tests that we can add to our svn.  Those particular tests
>> help us to verify some rather important Atom conformance features.
> 
> Agreed on both counts.  I generated the patch yesterday morning when my
> workstation couldn't get any response back from verisignlabs.  My
> immediate options were no build at all, a completely untested one, or a
> partially tested one.  
> 
> Further commentary: the patch doesn't disable the tests full stop -- it
> adds a  profile which has to be specifically enabled on the command line
> (e.g. mvn -P no-online-tests clean install); without the special
> incantation, all tests will still be run.  An alternate approach is to
> add the profile to one's local settings.xml.
> 
> cheers,
> 
> AC
> 
> 
> 
>