You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ant.apache.org by Stefan Bodewig <bo...@apache.org> on 2010/06/08 16:08:36 UTC

Re: Visual SourceSafe Antlib

On 2010-06-04, Bruce Atherton wrote:

> One downside to the way they are currently laid out is that you have
> to do a test build followed by a cleanup build every time (running Ant
> twice). Separating them out makes sense so that you have time between
> runs to examine the database and make sure everything is as
> expected. The trouble is that if you try to do two tests in a row
> without running cleanup in between, you get a build failure. Any ideas
> about how to fix that?

Can the tests depend on cleanup?  Sorry, I haven't actually looked into
the build file but thought I might toss out the idea anyway.

Stefan

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org


Re: Visual SourceSafe Antlib

Posted by Stefan Bodewig <bo...@apache.org>.
On 2010-06-08, Bruce Atherton wrote:

> On 08/06/2010 7:08 AM, Stefan Bodewig wrote:
>> Can the tests depend on cleanup?  Sorry, I haven't actually looked into
>> the build file but thought I might toss out the idea anyway.

> Sure they could, but then you couldn't examine the repository to make
> sure everything is being stored as expected.

If test depends on cleanup you can examine anything you want after
running the tests and things will get cleaned up before you run the next
tests.

Stefan

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org


Re: Visual SourceSafe Antlib

Posted by Bruce Atherton <br...@callenish.com>.
On 08/06/2010 7:08 AM, Stefan Bodewig wrote:
> Can the tests depend on cleanup?  Sorry, I haven't actually looked into
> the build file but thought I might toss out the idea anyway.
>    

Sure they could, but then you couldn't examine the repository to make 
sure everything is being stored as expected. Fine for automated tasks, 
but I like having the ability to manually look things over to make sure 
everything is as expected. Eventually the tests could become 
sophisticated enough to do the checking themselves, but for now they are 
pretty basic: Did calling the ss.exe command succeed or return an error 
code? If an error code, then the build fails.



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org