Ian:
>Good idea. Is there a way to force [Ignore]d tests to run ? It would be
>nice to have the regular build run the core tests and then a 'test-all'
>target that forces any questionable ones to run.
No there is not. Its been on my wishlist for a while now to have an option
in NUnit to "ignore
Good idea. Is there a way to force [Ignore]d tests to run ? It would be
nice to have the regular build run the core tests and then a 'test-all'
target that forces any questionable ones to run.
Our test output should probably also indicate the source of the problem
- ie 'cl.exe not detected on t
Gert:
>However, I agree that we should somehow find a solution for this problem
...
What if those tests were marked with the [Ignore] attrbute? That way it
will be clear that they are there (as they will show up in the NUnit
output as warnings) and then those who wish to run them, can simply un
; [EMAIL PROTECTED]
Subject: Re: [Nant-users] Failures:
Tests.NAnt.VisualCpp.Tasks.ClTaskTest_HelloWorld
I wonder if we could make this a bit nicer. There is an easy enough
work-around but for every person asking this question on the list the
are probably a few others giving up on using the tool
> - Original Message -
> From: "Ian MacLean" <[EMAIL PROTECTED]>
> To: "Gert Driesen" <[EMAIL PROTECTED]>
> Cc: "Michael Håkansson" <[EMAIL PROTECTED]>;
<[EMAIL PROTECTED]>
> Sent: Th
I wonder if we could make this a bit nicer. There is an easy enough
work-around but for every person asking this question on the list the
are probably a few others giving up on using the tool.
The quick and dirty way is to skip those tests by default. It would be
nicer to try to detect the locat
This means that the Visual C++ commandline tools, or libraries are not in
your path.
You can fix this by executing "C:\Program Files\Microsoft Visual Studio .NET
2003\Common7\Tools\vsvars32.bat" in the command prompt sessions in which
you're launching the NAnt build
But in fact you don't really h
