nunit-core team mailing list archive

[Charlie Poole <charlie@xxxxxxxxx>]

Hi Volkmar,

I guess we should document using the config as a workaround. The
reason it's only a
workaround and not a solution is that NUnit is intended to work while
running under
one framework and testing using another one.

The fact that the console worked properly using the /framework
argument would seem
to indicate that NUnit is not correctly detecting that the test
assembly is built for
.NET 4.0. This is surprising, since the detection is working in other cases.

It will help to know exactly which .NET framework versions are installed on
any systems where this problem is seen. NUnit detects all installed .NET
frameworks and acts (should act) accordingly.

Note that there is a bug in the case of Mono 4.0, which is not known to
NUnit as of this version.

Charlie

On Mon, Jul 5, 2010 at 1:58 AM, Volkmar  Nissen <v_nissen@xxxxxx> wrote:
> Hi,
>
> I faced the same issue.
>
> When I changed nunit-console.exe.config and added <startup>  <supportedRuntime version="4.0.30319" /></startup>
> and
>   <loadFromRemoteSources enabled="true" />
>  as  described above, the console version of NUnit worked properly when I added the /framwork=4.0.30319 option to the command line.
> A second start of the nunit console without /framework option was also successful.
>
> Starting the test using the GUI tool was never successful even after
> applying the neccessary changes in nunit.exe.config (The GUI version has
> no /framework option)
>
> what can I do to either further analyze the problem or to find some
> other solution?
>
> Volkmar
>
> --
> 2.5.5 cannot find fixture for framework 4.0
> https://bugs.launchpad.net/bugs/582051
> You received this bug notification because you are a member of NUnit
> Developers, which is subscribed to NUnit V2.
>

-- 
2.5.5 cannot find fixture for framework 4.0
https://bugs.launchpad.net/bugs/582051
You received this bug notification because you are a member of NUnit
Developers, which is subscribed to NUnit V2.

Status in NUnit V2 Test Framework: New

Bug description:
Just downloaded v2.5.5.10112 of Nunit. In a new VS2010 project I am unable to get either the nunit.exe or nunit-console.exe programs to recognize my test cases. The programs run, and after a while tell me 'can't find test fixture' in the case of nunit-console, and a similar message with nunit. The test class has TestFixture applied, and is public, the method has TestCase applied (started as Test) and is also public. The project has references to the 2.5.5 versions of nunit.core.dll and nunit.framework.dll.

I changed the target runtime to 3.5, recompiled, and it has picked up on the test cases immediately (I'm still using the 2.5.5 dlls).

Possibly of interest, the gui really wants to use version 2 of the framework. I tried requesting version 4 from the menu but after a while, it fails to find the test and reverts back to version 2 of the framework.

I'm using VS2010 (evaluation edition at the moment), on 64 bit Vista.

I've tried to find a solution elsewhere, and full apologies in advance if it's a school-boy error on my part.

Thanks for your time on the project.