Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

Welcome to Software Development on Codidact!

Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.

Comments on Test Extension Method Received Call with NSubstitute

Post

Test Extension Method Received Call with NSubstitute

+1
−0

How can I verify that an extension method was called when using NSubstitute for unit testing? For a normal method I'd do something like:

substitutedClass.Recieved().CheckedMethod(...)

But extension methods are not actually substituted so I can't use them with Received() in this way. For example if you use an ILogger with Microsoft.Extensions.Logging and try to check a call to LogWarning() like so:

logger.Received().LogWarning(Arg.Is<string>(s => s.Contains("special text")), Arg.Any<object?[]>());

you will get the following error since LogWarning() is an extension method:

NSubstitute.Exceptions.RedundantArgumentMatcherException : Some argument specifications (e.g. Arg.Is, Arg.Any) were left over after the last call.

This is often caused by using an argument spec with a call to a member NSubstitute does not handle (such as a non-virtual member or a call to an instance which is not a substitute), or for a purpose other than specifying a call (such as using an arg spec as a return value).

How can you test a call was received when an extension method was used?

History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.
Why should this post be closed?

1 comment thread

Extension methods are glorified static methods. AFAIK it is not possible to test that a static method... (1 comment)
Extension methods are glorified static methods. AFAIK it is not possible to test that a static method...
Alexei‭ wrote 4 months ago

Extension methods are glorified static methods. AFAIK it is not possible to test that a static method was called, regardless of what mocking library is used.

One way would be to check the call of a function called by the extension method.