6.0.1, NUnit 2.5.8 - tests execute twice, blow once, shown as failed? WHY?

Ok, this is seriously a followup to my other test.

more analysis showed I have 30 tests passed, 30 tests failed in one run. The same test executes twice, but I have no idea why.Unit test filter does not indicate why it should do so.

Basically the setup is:

Runtime : NUnit-2.5.8 MSIL
Run tests on : **/Rwe.Glori.*.Tests.dll
Collect .NET code coverage data with JetBrains dotCover

which is as easy as it gets. Anyone any idea why things are executed twice? Why one of htem blows consistently?

Example of a blown test:

PicklistManagerTests.GetPicklistId_AllSelectionsPresent (Rwe.Glori.StagingLo…oader.Database.Tests)Test history  
Assign responsibility  
Open in IDE  
show details »
« hide details

TearDown method failed. SetUp : System.IO.FileNotFoundException : Could not load file or assembly 'Oracle.DataAccess, Version=2.111.7.20, Culture=neutral, PublicKeyToken=89b483f429c47342' or one of its dependencies. The system cannot find the file specified.
TearDown : System.IO.FileNotFoundException : Could not load file or assembly 'Oracle.DataAccess, Version=2.111.7.20, Culture=neutral, PublicKeyToken=89b483f429c47342' or one of its dependencies. The system cannot find the file specified.
   at Rwe.Glori.StagingLoader.Database.Tests.ItemProcessorTest.Setup()
--TearDown
   at Rwe.Glori.StagingLoader.Database.Tests.ItemProcessorTest.Teardown()
« hide details

These is a clear missing oracle assembly which I copy into the proper foder via a post build event. AND... the same test is again there in the same run with a pass, so it does execute twice. It has two id's (47 and 77), jsut no indication WHY it blows.

Any help appreciated.

3 comments
Comment actions Permalink

Is your agent running on x64 OS? If so, it may be possible, that the assembly has native 32-bit dependencies, and cannot be loaded by x64 .NET runtime.
Try to change .NET Runtime Platform to x86 in NUnit runner settings.

Michael

0
Comment actions Permalink

Ok, that actually is at least logically part of the problem and explains it. I actually do have 32 bit native code and the server is 64 bit... while we develop on 32 bit

. Changed it to use the 32 bit runner for both nunit and code coverage. Sadly, results unchanged. Same thing still goes, results blow.

0
Comment actions Permalink

Do you still see the exception from your previous post?
Please attach full build log.

0

Please sign in to leave a comment.