You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Then adding com.example.MyClass.MyInternalClass to avoidCallsTo should (I assume) prevent the MyInternalClass.someMethod2(); from being mutated, which is not what happens.
Granted, this is not a common setup but it currently seems to be the most reasonable solution to exclude complex logging code from mutation (and code coverage).
The text was updated successfully, but these errors were encountered:
Assuming I have a class structure like this:
Then adding
com.example.MyClass.MyInternalClass
toavoidCallsTo
should (I assume) prevent theMyInternalClass.someMethod2();
from being mutated, which is not what happens.Granted, this is not a common setup but it currently seems to be the most reasonable solution to exclude complex logging code from mutation (and code coverage).
The text was updated successfully, but these errors were encountered: