I am not sure who to make this suggestion to but I would suggest renaming the
attribute 'testname' to something like 'testfixture' so it is a little clearer.
-Original Message-
From: Gifford, Noel [mailto:[EMAIL PROTECTED]
Sent: Monday, July 26, 2004 9:49 PM
To: Burton, Kevin; [EMAIL PROT
>From my investigations it doesn't appear possible to automate at a
granularity smaller than a TestFixture.
Is there a compelling reason why the TestFixture can't be separated into
multiple TestFixtures. The TestFixture class doesn't have any bearing
on what's actually contained in it or, to a la
But the [TestFixture] contains about 100 [Test]'s. I want to run just a few of the
[Test]'s. Is that not possible?
-Original Message-
From: Gifford, Noel [mailto:[EMAIL PROTECTED]
Sent: Monday, July 26, 2004 7:25 PM
To: Burton, Kevin; [EMAIL PROTECTED]
Subject: RE: [Nant-users] Nunits tas
Thank you! That did it.
--
Edwin G. Castro
Firing Systems Engineer
[EMAIL PROTECTED]
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
> Troy Laurin
> Sent: Monday, July 26, 2004 5:42 PM
> To: Nant-Users
> Subject: RE: [Nant-users] task using
> > - Original Message -
> > From: "Castro, Edwin Gabriel (Firing Systems Engr.)"
> <[EMAIL PROTECTED]>
> > To: "Nant-Users" <[EMAIL PROTECTED]>
> > Sent: Saturday, July 24, 2004 1:50 AM
> > Subject: [Nant-users] task using
> >
> >
> > I'm trying to do the following:
> >
> >
> >
>
Kevin,
Attached is a zip of a project with NUnit working.
The testname attribute must be the full namespace and include the class
name. If it is just the namespace or ends in a method, then the error
you see is returned.
It looks like the testname attribute must actually refer to the
[TestFixtu
I don't think you need the config file. I don't use one.
You do need to ensure that your DLLs are built using the same version of
NUnit that is eventually used to run the unit tests.
Noel
I do the following:
The documentation indicates that I need to add some lines to the test application
config file. I didn't have an application config file so I created one:
The name of the DLL is TandemTests.DLL so the conf
Noel
Thank you.
I'm looking forward to using your checklist, the first 4 steps are priceless,
and very much needed.
Adding that together with Troys comments about how to point NAnt at NAnt
Contrib give us (what I think is) the start of a good user-smoke-test.
Like I said, the first 4 steps ar
Troy
Your post is fantastic, to the point, wonderful, and among the best quick howto
on NAntContrib that I have seen.
The sad thing is that I NEVER would have happened upon that post on my own.
The only reason I have installed NantContrib where I did was because
A) people said to
B) I couldn't
Gert,
I was using the following version:
NAnt 0.85 (Build 0.85.1653.0; net-1.0.win32; nightly; 7/11/2004)
That's a fairly old version by now. Using a new nightly won't be too
much of a problem.
At least your response implies that my syntax is correct. I'll post
again, if the newest nightly stil
>From: "John Ludlow" <[EMAIL PROTECTED]>
>Sent: Monday, July 26, 2004 5:16 AM
>copy "$(ProjectDir)ServerUnitTesting.dll.config"
"$(ProjectDir)\$(OutDir)ServerUnitTesting.dll.config"
...
>copy "$(ProjectDir)ServerUnitTesting.dll.config"
"$(ProjectDir)\$(OutDir)ServerUnitTesting.dll.config"
I think
> Can you provide a small repro for this issue ?
Gyaaaghh!!!
Ok, I figured out how to output stuff from the build event (echo command, just like
DOS) and found out where it was going wrong.
The build event looks like this:
copy "$(ProjectDir)ServerUnitTesting.dll.config"
"$(ProjectDir)\$(OutD
unsubscribe
14 matches
Mail list logo
