I'm new to mbunit and have been porting a few tests from MSTest to see
whether this is the platform for me. One thing that struct me as odd
is that if I pass a null into Assert.AreEqual to compare against a
properly initialised object, the code never returns out of the
AreEqual - it just hangs there.

Is this expected behaviour as I find it surprising? Or perhaps a
problem connected to running them through the coderush test runner and
not Gallio 3.1.397?

Dan

Hi Dan,

The assertion is definitely not supposed to hang. I daily run tens of
thousands assertions of that kind for my own projects at work and at home
without any problem. There is certainly something else which causes the
problem.

   - Does your type implement an equality mechanism? (IEquatable<T>,
   equality operator overload, or just Object.Equals). It's sometimes tricky. I
   remember buggy implementations of mine which caused infinite loops or stack
   overflows (especially with an equality operator overload combined with a
   null checking by using == in the Object.Equals override!)
   - You also mention the coderush test runner. We do not provide any test
   runner for coderush (and in fact I didn't know it was possible to run tests
   within coderush). So it is possible that there is an issue here (3rd party
   test runner?). Could you try to run the same test within any other test
   runner (like Icarus, Echo, TD.Net, R#, etc.)
   - Or do you mean the Visual Studio test runner? (i.e. the same you use
   for MSTest) Which version of VS are you using?

Also, could you please try Gallio 3.2 RC
<http://gallio.org/Downloads.aspx>as v3.1 do not support some "new"
versions of certain 3rd party s/w like
VS2010, R# 5.x, NUnit 2.5.4 and later, etc. (usually because their test
model or their extensibility model has changed)

Ultimately, please send to us a screenshot, and perhaps a sample code which
demonstrate the issue?

Regards,
Yann

2010/7/19 Daniel Harman <daniel.a.har...@gmail.com>