Class: matlab.unittest.qualifications.FatalAssertable
Package: matlab.unittest.qualifications
Fatally assert function issues no warnings
fatalAssertWarningFree(fatalAssertable,actual)
fatalAssertWarningFree(fatalAssertable,actual,diagnostic)
[output1,...,outputN] = fatalAssertWarningFree(___)
fatalAssertWarningFree( fatally
asserts that fatalAssertable,actual)actual is a function handle that
issues no warnings.
fatalAssertWarningFree( also displays the diagnostic information in fatalAssertable,actual,diagnostic)diagnostic upon
a failure.
[ also
returns the output arguments output1,...,outputN] = fatalAssertWarningFree(___)output1,...,outputN that
are produced when invoking actual.
|
The |
|
The function handle to test. |
|
Diagnostic information related to the qualification, specified as one of the following:
Diagnostic values can be nonscalar. For more information, see |
|
Output arguments, 1 through n (if any), from |
See examples for verifyWarningFree, and replace calls to verifyWarningFree with fatalAssertWarningFree.
This method is functionally equivalent to:
import matlab.unittest.constraints.IssuesNoWarnings; fatalAssertable.fatalAssertThat(actual, IssuesNoWarnings());
There exists more functionality when using the IssuesNoWarnings constraint
directly via fatalAssertThat.
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. Alternatively,
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 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 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.