+972 52-548-6969Bug 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
Oren Eini aka Ayende Rahien
CEO of Hibernating Rhinos LTD,
which develops RavenDB,
a NoSQL Open Source Document Database.
FUTURE POSTS
- Managing delays in distributed systems with RavenDB - 17 hours from now
There are posts all the way to Nov 28, 2022
RECENT SERIES
-
Recording
(6):
17 Nov 2022 - RavenDB in a Distributed Cloud Environment -
RavenDB Indexing
(2):
20 Oct 2022 - exact() -
Production postmortem
(45):
03 Oct 2022 - Do you trust this server? -
Webinar recording
(15):
26 Aug 2022 - Modeling Relationships and Hierarchies in a Document Database -
re
(32):
16 Aug 2022 - How Discord supercharges network disks for extreme low latency
RECENT COMMENTS
-
By peter on RavenDB Index Cleanup feature
-
By Zahid Aramai on RavenDB indexing: exact()
-
By Oren Eini on RavenDB indexing: exact()
-
By CHristiaanS on RavenDB indexing: exact()
-
By Alois Kraus on Error handling in the field
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