Main Content

verifyLessThan

Class: matlab.unittest.qualifications.Verifiable
Package: matlab.unittest.qualifications

Verify value is less than specified value

Syntax

verifyLessThan(verifiable,actual,ceiling)
verifyLessThan(___,diagnostic)

Description

verifyLessThan(verifiable,actual,ceiling) verifies that all elements of actual are less than all the elements of ceiling.

verifyLessThan(___,diagnostic) also associates the diagnostic information in diagnostic with the qualification. Depending on the test runner configuration, the testing framework might display diagnostics when the qualification passes or fails. By default, the framework displays diagnostics only when the qualification fails. You can override the default behavior by customizing the test runner. For example, use a DiagnosticsOutputPlugin instance to display both failing and passing event diagnostics.

Input Arguments

verifiable

The matlab.unittest.TestCase instance which is used to pass or fail the verification in conjunction with the test running framework.

actual

The value to test. actual must be the same size as ceiling unless either one is scalar, at which point scalar expansion occurs.

ceiling

Maximum value, exclusive.

diagnostic

Diagnostic information related to the qualification, specified as one of the following:

  • string array

  • character array

  • function handle

  • matlab.unittest.diagnostics.Diagnostic object

Diagnostic values can be nonscalar. For more information, see matlab.unittest.diagnostics.Diagnostic.

Examples

expand all

Create a TestCase object for interactive testing.

testCase = matlab.unittest.TestCase.forInteractiveUse;

Verify 2 is less than 3.

verifyLessThan(testCase, 2, 3);
Interactive verification passed.

Test if 9 is less than 5.

verifyLessThan(testCase, 9, 5);
Interactive verification failed.

---------------------
Framework Diagnostic:
---------------------
verifyLessThan failed.
--> The value must be less than the maximum value.

Actual Value:
         9
Maximum Value (Exclusive):
         5

Test failed.

Test if each element is less than the CEILING value, 9.

testCase = matlab.unittest.TestCase.forInteractiveUse;
verifyLessThan(testCase, [5 6 7], 9);
Interactive verification passed.

Test if each element in the matrix is less than the CEILING value, 4.

verifyLessThan(testCase, [1 2 3; 4 5 6], 4);
Interactive verification failed.

---------------------
Framework Diagnostic:
---------------------
verifyLessThan failed.
--> Each element must be less than the maximum value.
    
    Failing Indices:
             2     4     6

Actual Value:
         1     2     3
         4     5     6
Maximum Value (Exclusive):
         4

Test failed.

Test if each element is less than each corresponding element of the CEILING array, [7 -1 8].

testCase = matlab.unittest.TestCase.forInteractiveUse;
verifyLessThan(testCase, [5 -3 2], [7 -1 8]);
Interactive verification passed.

Compare an array to itself.

verifyLessThan(testCase, eye(2), eye(2));
Interactive verification failed.

---------------------
Framework Diagnostic:
---------------------
verifyLessThan failed.
--> Each element must be less than each corresponding element of the maximum value array.
    
    Failing Indices:
             1     2     3     4

Actual Value:
         1     0
         0     1
Maximum Value (Exclusive):
         1     0
         0     1

Test failed.

Tips

  • This method is functionally equivalent to:

    import matlab.unittest.constraints.IsLessThan;
    verifiable.verifyThat(actual, IsLessThan(ceiling));

    There exists more functionality when using the IsLessThan constraint directly via verifyThat.

  • 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 qualification 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. Alternatively,

    • 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. For more information, see matlab.unittest.qualifications.Assumable.

    • 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 renders the current test method as failed and incomplete. For more information, see matlab.unittest.qualifications.Assertable.

    • 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. For more information, see matlab.unittest.qualifications.FatalAssertable.

Introduced in R2013a