+972 52-548-6969
Bug of the day...
time to read 1 min | 13 words
Using MbUnit 2.4, this test pass:
Guid g = Guid.Empty; Assert.AreEqual(Guid.Empty, g); Assert.AreNotEqual(Guid.Empty, g);
FUTURE POSTS
- Optimizing the cost of clearing a set - about one day from now
- Scaling HNSW in RavenDB: Optimizing for inadequate hardware - 3 days from now
There are posts all the way to May 14, 2025
RECENT SERIES
-
RavenDB News
(2):
02 May 2025 - May 2025 -
Recording
(15):
30 Apr 2025 - Practical AI Integration with RavenDB -
Production Postmortem
(52):
07 Apr 2025 - The race condition in the interlock -
RavenDB
(13):
02 Apr 2025 - .NET Aspire integration -
RavenDB 7.1
(6):
18 Mar 2025 - One IO Ring to rule them all
RECENT COMMENTS
-
By Samyon Ristov on The null check that didn't check for nulls
-
By Johannes Egger on The null check that didn't check for nulls
-
By riccardo on The null check that didn't check for nulls
-
By Chris B on The null check that didn't check for nulls
-
By Tim on When racing the Heisenbug, code quality goes out the Windows
Syndication
| Main feed | |
| Comments feed |
Comments
well that's helpful
Yep, ran into that one a while ago...
http://code.google.com/p/mb-unit/issues/detail?id=114
It's funny that I have stumbled in the exactly same bug today.
Well, seems almost no one is actually using AreNotEqual if this lived to the 2.4.
Thanks Oren, I'll need to investigate this more but I think in the absence of an assert for Guid that MbUnit is casting to object and then equating as a null. The AreNotEqual has this gem.
if (expected == null ^ actual == null)
return;
As both become null in the cast it passes. Thats a complete guess at the moment until I can investigate more. Always fun.
Andy
Maybe it been updated since the version I'm running (1.0.2700) but the real problem I see is that AreEqual(object, object) uses the object's Equals() methods (via ObjectsEqual) which is customized to the class, while AreNotEqual just uses !(obj==obj) which ultimately just Object.ReferenceEquals.
That's because GUIDs are so unique that even two identical GUIDs are not quite equal. Duh.
That's nothing compared to my bug of the day:
try running this piece of code in the immediate window and then in the body of a funcion.
bool a = object.ReferenceEquals("A","A")
a would be true as the compiler would have inturned the string "A"
Comment preview