Some test cases have multiple MockBehavior values defined, expanding the number of test cases used.
This is
Inconsistent between analyzer tests
Does not change the analyzer behavior
That is, there is no difference between MockBehavior.Default, MockBehavior.Loose, and MockBehavior.Strict. There is a difference between not specifying a mock behavior and specifying a behavior. Tests should have one of each constructor
Default (no args)
Specifying a MockBehavior (e.g., MockBehavior.Default)
Where applicable (e.g., ConstructorArgumentsShouldMatchAnalyzer):
Specifying constructor parameters
Specifying a MockBehaviorand also specifying constructor parameters
Some test cases have multiple
MockBehavior
values defined, expanding the number of test cases used.This is
That is, there is no difference between
MockBehavior.Default
,MockBehavior.Loose
, andMockBehavior.Strict
. There is a difference between not specifying a mock behavior and specifying a behavior. Tests should have one of each constructorMockBehavior
(e.g.,MockBehavior.Default
)Where applicable (e.g.,
ConstructorArgumentsShouldMatchAnalyzer
):MockBehavior
and also specifying constructor parameters