-
Notifications
You must be signed in to change notification settings - Fork 11
Conversation
{ | ||
var actualValue = input.IsPullRequest(); | ||
|
||
Assert.AreEqual(expectedValue, actualValue); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm quite a fan of Shouldly for assertions. input.IsPullRequest().ShouldBe(expectedValue)
will give quite good error messages.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'll give you this one. It's all a matter of preference, to be honest I think nunit provides really good feedback (I expected x, but got y). Not sure how shouldly does it but I'll do it anyway.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Shouldly actually grabs the source code from your code to use in the assertion. It should give better error messages in all cases :)
@JakeGinnivan All changes I think should be made are made. |
Nice! |
Supress CS0414: The private field 'field' is assigned but its value is never used. Supress CS1701: Assuming assembly reference "Assembly Name GitTools#1" matches "Assembly Name GitTools#2", you may need to supply runtime policy.
No description provided.