Class: matlab.unittest.qualifications.Assumable
Package: matlab.unittest.qualifications
Assume function throws specified exception
assumeError(assumable,actual,identifier)
assumeError(assumable,actual,metaClass)
assumeError(___,diagnostic)
[output1,...,outputN] = assumeError(___)
assumeError(
assumes that assumable
,actual
,identifier
)actual
is a function handle that throws
an exception with an error identifier that is equal to identifier
.
assumeError(
assumes that assumable
,actual
,metaClass
)actual
is a function handle that throws
an exception whose type is defined by the meta.class
instance
specified in metaClass
. This method does not
require the instance to be an exact class match, but rather it must
be in the specified class hierarchy, and that hierarchy must include
the MException
class.
assumeError(___,
also displays the diagnostic information in diagnostic
)diagnostic
upon
a failure.
[output1,...,outputN] = assumeError(___)
returns multiple output arguments from the invocation of the function handle actual
. Use this syntax to control the number of output arguments requested from the function handle. If the function handle errors, all outputs are of type missing
. Otherwise, output1,...,outputN
are output values from actual
. You can use this syntax with any of the input arguments of the previous syntaxes.
|
The |
|
The value to test. |
|
Error identifier, specified as a character vector. |
|
An instance of |
|
Diagnostic information related to the qualification, specified as one of the following:
Diagnostic values can be nonscalar. For more information, see |
See examples for verifyError
, and replace calls to
verifyError
with assumeError
.
This method is functionally equivalent to:
import matlab.unittest.constraints.Throws; assumable.assumeThat(actual, Throws(identifier)); assumable.assumeThat(actual, Throws(metaClass));
There exists more functionality when using the Throws
constraint directly via assumeThat
.
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
. Alternatively,
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. For more information, see matlab.unittest.qualifications.Verifiable
.
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
.