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.

Post History

60%
+1 −0
Q&A Test Extension Method Received Call with NSubstitute

Extension methods can't be tested for received calls as they are not directly on the substituted class, plus they are static. However, extension methods are ultimately calling into a real method o...

posted 5mo ago by rcmosher‭

Answer
#1: Initial revision by user avatar rcmosher‭ · 2024-07-16T00:10:39Z (5 months ago)
Extension methods can't be tested for received calls as they are not directly on the substituted class, plus they are `static`.

However, extension methods are ultimately calling into a real method on the class that is substituted. You can still test that method is called.

This takes extra digging to find the actual method called. For instance `Microsoft.Extensions.Logging` extension methods eventually call into `Log<TState>(LogLevel logLevel, EventId eventId, TState state, Exception? exception, Func<TState, Exception?, string> formatter)`

We can test for calls to this with:

    logger.Received().Log(
        LogLevel.Warning,
        Arg.Any<EventId>(),
        Arg.Is<object>(x => (x.ToString() ?? string.Empty).Contains("special text")),
        Arg.Any<Exception?>(),
        Arg.Any<Func<object, Exception?, string>>());

The logging extensions shows an example of an extra challenge. They pass a parameter that is `interal`, `FormattedLogValues`. We can't specify this as the type passed with `Arg.Is<FormattedLogValues>()` as we don't have access to it. But as you can see in the example above we can check it against `object`, and, having discovered `FormattedLogValues` is just a wrapper for the logged string, get its string value and test against that.