+972 52-548-6969
TestDriven.Net + MbUnit Gotcha
time to read 2 min | 221 words
That caused some issues.
I just run into a hairy issue in using TestDriven.Net and MbUnit. For some reason, none of my [SetUp] methods would run. I have moved machine with a project, and on the desktop, everything was peachy, on my laptop, [SetUp] doesn't work.
I am using MbUnit version: 1.0.2614.40165
And here is the test output:
MbUnit 1.0.2642.28107 Addin
No tests found
Starting the MbUnit Test Execution
Exploring Tests.Integration, Version=0.1.248.0, Culture=neutral, PublicKeyToken=null
MbUnit 1.0.2642.28107 Addin
No tests found
TestCase 'M:Tests.Integration.Policy.NewPolicy.MakeOrBreak'
failed: Object reference not set to an instance of an object.
System.NullReferenceException: Object reference not set to an instance of an object.
Tests.Integration\BaseWebTest.cs(117,0): at Extranet.Tests.Integration.BaseWebTest.ClickLink(String partialElementId)
No tests found
Starting the MbUnit Test Execution
Exploring Tests.Integration, Version=0.1.248.0, Culture=neutral, PublicKeyToken=null
MbUnit 1.0.2642.28107 Addin
No tests found
TestCase 'M:Tests.Integration.Policy.NewPolicy.MakeOrBreak'
failed: Object reference not set to an instance of an object.
System.NullReferenceException: Object reference not set to an instance of an object.
Tests.Integration\BaseWebTest.cs(117,0): at Extranet.Tests.Integration.BaseWebTest.ClickLink(String partialElementId)
The issue was a version mismatch, yuck! This doesn't usually happen on NUnit because NUnit is very version tolerant, and it looks like MbUnit is much less so.
Comments
Comment preview