Mocking a static method not directly used in a test execution logic messes with the arrangements of the test
Mocking a method that is not used in the test execution logic could lead to unwanted recursive mocking behavior for the rest of the methods in the class. The unwanted behavior could later result in an exception if the affected methods are called during the arrangement of another method.
Posted on:02 Dec 2019 10:35
This issue is fixed and is available with the R3 2019 Service Pack (2019.3.1028.2) release.
Do you want to have your say when we set our development plans?
Do you want to know when a feature you care about is added or when a bug fixed?
Telerik Feedback Portal
and vote to affect the priority of the items