verifyNotCalled

Class: matlab.mock.TestCase
Package: matlab.mock

Verify that a method was not called with certain input values

expand all in page

Syntax

verifyNotCalled(testcase,behavior,diagnostic)

Description

verifyNotCalled(testcase,behavior,diagnostic) verifies that a method was not called with certain input values.

Input Arguments

expand all

Instance of the test case, specified as a matlab.mock.TestCase object.

Behavior of the mock, specified as a matlab.mock.MethodCallBehavior instance. To create an instance of matlab.mock.MethodCallBehavior, call a method of the behavior object.

Example: withExactInputs(myMockBehavior.myMockedMethod)

Diagnostic information to display, specified as a string array, character array, function handle, or matlab.unittest.diagnostics.Diagnostic object. Diagnostic values can be nonscalar. For more information, see matlab.unittest.diagnostics.Diagnostic.

Example: "My diagnostic message."

Example: @() datetime('now')

Examples

expand all

Verify a method was not called.

testCase = matlab.mock.TestCase.forInteractiveUse;
[mock,behavior] = testCase.createMock('AddedMethods',"foo");
mock.foo(123);

Test passing cases.

testCase.verifyNotCalled(behavior.foo(456));
testCase.verifyNotCalled(withExactInputs(behavior.foo));

Test failing cases.

testCase.verifyNotCalled(behavior.foo(123));
testCase.verifyNotCalled(behavior.foo(123), ...
    'Method foo should not have been called with input 123.');

Tips

Use verification qualifications to produce and record failures without throwing an exception. Since verifications do not throw exceptions, all test content runs to completion even when verification failures occur. Typically verifications are the primary qualifications for a unit test since they typically do not require an early exit from the test. Use other qualification types to test for violation of preconditions or incorrect test setup.

  • Use assumption qualifications to ensure that the test environment meets preconditions that otherwise do not result in a test failure. Assumption failures result in filtered tests, and the testing framework marks the tests as Incomplete.

  • Use assertion qualifications when the failure condition invalidates the remainder of the current test content, but does not prevent proper execution of subsequent test methods. A failure at the assertion point marks the current test method as failed and incomplete.

  • Use fatal assertion qualifications to abort the test session upon failure. These qualifications are useful when the failure mode is so fundamental that there is no point in continuing testing. These qualifications are also useful when fixture teardown does not restore the MATLAB® state correctly and it is preferable to abort testing and start a fresh session.

Alternatives

Using the verifyNotCalled method is functionally equivalent to using the negated matlab.mock.constraints.WasCalled constraint with the verifyThat method of the Verifiable class. For example, the following code blocks are functionally equivalent.

% Using the verifyNotCalled method
testCase.verifyNotCalled(behavior.foo(456), ...
    'Method foo should not have been called with input 456.')

% Using the WasCalled constraint with verifyThat method
import matlab.mock.constraints.WasCalled;
testCase.verifyThat(behavior.foo(456),~WasCalled, ...
    'Method foo should not have been called with input 456.')
However, there is more functionality when you use the WasCalled constraint. For instance, you can specify a method was not called a certain number of times.

See Also

Introduced in R2017a

Was this topic helpful?
MATLAB Documentation
Support