Re: The NUnit reference goes away with Clean builds

On Thu, Apr 3, 2008 at 10:38 AM, Brad Stiles <[email protected]> wrote:
> Kelly Anderson <[email protected]> wrote:
>
>  > If NUnit isn't installed, then how do you run your tests? Do you
>  > reinstall NUnit as part of your build process? If so, then how do you
>  > do your build?
>
>  Export the toolset from the repository and execute the unit tests using
>  the exported one.  I've used this method, but now I just have it
>  installed on the build server.  Every application needing to export the
>  same toolset, when we don't change the versions of that toolset very
>  often, seemed somewhat wasteful to me.

When you say repository, you're meaning the revision control system?
Are you saying that you put NUnit.exe into the revision control, fetch
it and execute it from there? So, in other words, you don't have any
of the developers or the build machine actually install NUnit with an
MSI, but rather just fetch the files out of revision control. Is that
what you're saying here?

>  When we *do* change, we drop the new version on the build server, in the
>  same named directory as the old one, i.e. "NUnit", the bin directory of
>  which is in the path, and proceed.  Build servers and local machines are
>  set up with the toolset installed in the same location, e.g.
>  "c:\devtools", so paths work out.  If we kept it in the repo, or put
>  each version of the NUnit assembly in the GAC on the build servers, we
>  wouldn't have to do that.
>
>  Like you, we found that setting the "specific version" flag to false
>  alleviated the problem of new versions of NUnit running against older
>  tests.  Fortunately NUnit is pretty healthy in the backwards-compatible
>  department.

That does seem to help, but if you got the current NUnit out of
revision control, then why would you have to do that?

>  Note that the build toolset is installed in a different directory than
>  the one in which the builds themselves happen, so when a clean happens
>  on the build directory, nothing happens to the toolset.

I may not be understanding what you mean by toolset here. I'm still a
bit foggy, sorry.

-Kelly

-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace