We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Shouldly correctly compares the millisecond portion of DateTimeOffset, but does not display it in the message.
DateTimeOffset
[Fact] public void Test() { var dateTimeOffset1 = new DateTimeOffset(new DateTime(2023, 12, 01, 01, 01, 01, 123)); var dateTimeOffset2 = new DateTimeOffset(new DateTime(2023, 12, 01, 01, 01, 01)); dateTimeOffset1.ShouldBe(dateTimeOffset2); }
For comparison, here is the fluent assertions output:
The text was updated successfully, but these errors were encountered:
+1 I just had this same problem and it really threw me for a bit
Sorry, something went wrong.
No branches or pull requests
Shouldly correctly compares the millisecond portion of
DateTimeOffset
, but does not display it in the message.For comparison, here is the fluent assertions output:
The text was updated successfully, but these errors were encountered: