Comment 5 for bug 582051

Charlie,

 From the first comment, yes, as ever it could be user error, but is
there something different I would need to do to run from 2.5.5 compared
to 2.4.8? I've always had success there. I follow a simple pattern of
setting up the debug executable to be nunit.exe, I then set the command
line arguments to just the name of the .dll file (no directories or
anything else).

Since I started using it I have run into the problem of the debugger not
attaching to the correct process, I made the modifications listed here:
http://frater.wordpress.com/2010/05/04/debugging-nunit-tests-under-visual-studio-2010/
and it appears to be working.

This may, of course, mean that I'm not testing against the problem I
think I saw last night. If anyone comes back to you with the same
problem, then please do come back to me if I can help further.

Another problem that may become more common is I think that nunit agent
listens on an IP address. My AV (PC-Cillin) didn't like that one bit and
reckoned that it was something highly suspect. I re-assured it, but look
out for future bug reports in this area.

Thanks,

Martin

Charlie Poole wrote:
> One possibility is that your setup to execute NUnit as a debug app was not
> quite right at one time. This is very easy to do. :-)
>
> Yes, this is a good place to continue the discussion until/unless we decide
> it's actually an NUnit bug.
>
> Charlie
>
> On Tue, May 18, 2010 at 3:31 PM, Martin Jones
> <email address hidden>wrote:
>
>> Hi Jv,
>>
>> Thanks for the quick response, and can I just quickly say thankyou,
>> thankyou very much for nunit.
>>
>> I'm having trouble repeating the bug this morning, I remember that there
>> was something I left off the report last night that might be useful. Let
>> me explain what I have done first though.
>>
>> The VS solution is in SVN so I checked it out to a 32 bit machine, and
>> left it in it's current 'target framework 3.5' position and it worked
>> fine. I changed the solution to target to framework 3.5 and it worked
>> fine as well. All of the target changes are on the VS projects, not nunit.
>>
>> I went back to the 64 bit machine, reloaded the project and checked that
>> it still worked with a framework 3.5 target. It did. I then changed it
>> to a 4.0 project and it worked! I do not believe that anything else had
>> changed.
>>
>> In case there was something being affected by it having run once, I
>> created a new 64 bit, very simple test project, and it ran fine.
>>
>> In all these cases I am running a class library by setting the debug
>> executable to nunit.exe and giving it the name of the .dll containing
>> the testing code - I don't use an .nunit file.
>>
>> So, I have been unable to repeat the issue I was having last night. I'm
>> sure you get some bogus bug reports, and I'll be the first one to admit
>> that I can make silly mistakes, but I really haven't made any changes
>> from last night other than moving it back to a framework 4.0 target.
>>
>> Last night, there was one odd thing that happened while initially trying
>> to get nunit running. I had the error about not finding the test fixture
>> on the very first run. On the second attempt, I believe it found the
>> text fixture, but not on any subsequent runs. I believe that it was the
>> nunit 2.5.5 version that was running because visually it appeared
>> slightly different (with the tick marks) to 2.4.8 that I had been using
>> previously. The reason that I didn't include it in the report last night
>> was that I was working with two solutions and assumed that I had
>> accidently run an old solution where I was copying the using statements
>> from. Because I couldn't repeat it - I put it down to this other
>> solution and assumed that I was mistaken. I'm not so sure now.
>>
>> My solution is now set to framework 4.0 and I will be using nunit
>> 2.5.5.10112 for the next couple of days. If I can reproduce the error
>> once more, then I will let you know. If I do reproduce the error, should
>> I reply to this email again?
>>
>> Martin
>>
>>
>> Jv wrote:
>>> Hi Martin,
>>>
>>> I installed VS 2010 Ultimate in my machine to replicate your bug scenario
>>> but it works in my machine properly. I saved the .nunit project file in
>> the
>>> bin\debug folder of my VS 2010 test project using Nunit 2.5.10112. I ran
>> the
>>> tests using the default project settings, which says use the default
>> version
>>> of the framework (which will translate to whichever framework against
>> which
>>> the test assembly has been compiled with) and it works absolutely fine.
>>>
>>> So, the only difference seems to be in your 64 bit machine. I will try to
>>> replicate the scenario in a 64-bit machine and let you know. kindly reply
>> if
>>> the assembly gets loaded on a 32 bit machine then we will be sure that it
>> is
>>> something specific to 64-bit machines.
>>>
>>> Regards,
>>>
>>> Jv
>>> http://ravichandranjv.blogspot.com
>>> On Tue, May 18, 2010 at 9:20 AM, Martin Jones <<email address hidden>
>>> wrote:
>>>
>>>> Public bug reported:
>>>>
>>>> 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.
>>>>
>>>> ** Affects: nunitv2
>>>> Importance: Undecided
>>>> Status: New
>>>>
>>>> --
>>>> 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.
>>>>
>>>>
>>>>
>>>
>> --
>> 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.
>>
>