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);
Ayende @ Rahien
Ayende @ Rahien
Hi!
My name is Oren Eini
Founder of Hibernating Rhinos LTD and RavenDB.
You can reach me by email or phone:
My name is Oren Eini
Founder of Hibernating Rhinos LTD and RavenDB.
You can reach me by email or phone:
+972 52-548-6969
FUTURE POSTS
No future posts left, oh my!
RECENT SERIES
-
RavenDB 4.0
(13):
11 Sep 2017 - Support options -
Optimizing select projections
(5):
01 Sep 2017 - Part IV–Understand, don’t do -
Optimizing JavaScript and solving the halting problem
(2):
18 Aug 2017 - Part II -
Public Service Announcement
(2):
11 Aug 2017 - ConcurrentDictionary.Count is locking -
PR Review
(4):
10 Aug 2017 - Errors, errors and more errors
RECENT COMMENTS
-
By Tyler Jensen on Leaning on the compiler
-
By Oleg Mihailik on You are judged on what is above the waterline
-
By njy on You are judged on what is above the waterline
-
By Eric Smith on You are judged on what is above the waterline
-
By Pop Catalin on You are judged on what is above the waterline
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