added ILoggerTests to ensure NSubstitute can be used to test specific ILogger calls happened. #732
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.
#634 talks about wanting to use NSubstitute to validate a call into
Microsoft.Extensions.Logging.ILogger
. I have the same need and found that the newArg.AnyType
is insufficient to solving this problem.So I've added a new test class that shows a number of scenarios using
LoggerExtensions
extension methods fromMicrosoft.Extensions.Logging.ILogger
. The tests include:As you'll see, I had to change how
TypesAreAllEquivalent
works to handle theFunc<TState, Exception?, string>
used by ILogger.