Nikolai's team experienced an intermittent build failure in their CI/CD pipeline, with tests failing approximately 0.5% of the time. This annoyance prompted Nikolai to investigate the issue independently. The failing test was related to Microsoft's GUID implementation, which is a wrapper for UUID algorithms. The specific assertion was Assert.DoesNotContain("000", transactionId.ToString());, which checked if a GUID string contained "000". This was intended to detect an empty UUID, but the assumption that "000" would never appear in a valid GUID string was incorrect. Nikolai discovered that this string representation occurred 0.5527% of the time, roughly once in every 181 instances. The test was poorly designed and could be improved with a more robust check. A better approach would be to utilize the built-in GUID.Empty constant, which represents a UUID with all bits set to zero. The author expresses frustration that developers might not use such obvious constants, suggesting that consulting documentation would likely reveal their existence. The article includes an advertisement for a NuGet guide.
Assert.DoesNotContain("000", transactionId.ToString());, which checked if a GUID string contained "000". This was intended to detect an empty UUID, but the assumption that "000" would never appear in a valid GUID string was incorrect. Nikolai discovered that this string representation occurred 0.5527% of the time, roughly once in every 181 instances. The test was poorly designed and could be improved with a more robust check. A better approach would be to utilize the built-inGUID.Emptyconstant, which represents a UUID with all bits set to zero. The author expresses frustration that developers might not use such obvious constants, suggesting that consulting documentation would likely reveal their existence. The article includes an advertisement for a NuGet guide.