Ensure SUT's variable name is logged #87
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
adrianiftode
force-pushed
the
fixes-ensure-SUT-variable-name-is-logged
branch
2 times, most recently
from
cb81e80
to
ddfc2f5
Compare
Instead of showing 'Expected response to have'
it was shown 'Expected value to have'
when the assertion was like response.Should().XXX
inline all ExecuteAssert private methods
change from {context:value} to {context:response}
add CustomAssertion attribute
adrianiftode
force-pushed
the
fixes-ensure-SUT-variable-name-is-logged
branch
from
ddfc2f5
to
58822f6
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Instead of showing 'Expected response to have'
it was shown 'Expected value to have'
when the assertion was like response.Should().XXX