matlab.unittest.qualifications.Verifiable.verifyFalse - Verify value is false - MATLAB (original) (raw)

Class: matlab.unittest.qualifications.Verifiable
Namespace: matlab.unittest.qualifications

Syntax

Description

verifyFalse([testCase](#bt00p%5F2-1%5Fsep%5Fmw%5F8d5e73c7-bacb-46a7-a1c1-f24af91e6c03),[actual](#mw%5F7c9f81a9-c0a5-474b-8f85-456fe4cde2e1)) verifies that the value of actual is logical 0 (false).

example

verifyFalse([testCase](#bt00p%5F2-1%5Fsep%5Fmw%5F8d5e73c7-bacb-46a7-a1c1-f24af91e6c03),[actual](#mw%5F7c9f81a9-c0a5-474b-8f85-456fe4cde2e1),[diagnostic](#mw%5F3e9cbe2b-503b-4ae2-a7b4-929b7a8b783c)) also associates the diagnostic information in diagnostic with the qualification.

example

Input Arguments

expand all

Test case, specified as a matlab.unittest.qualifications.Verifiable object. Because the matlab.unittest.TestCase class subclasses matlab.unittest.qualifications.Verifiable and inherits its methods, testCase is typically amatlab.unittest.TestCase object.

Value to test, specified as a value of any data type. Although you can provide a value of any data type, the test fails if actual is not a logical scalar with a value of false.

Diagnostic information to display when the qualification passes or fails, specified as a string array, character array, function handle, or array of matlab.automation.diagnostics.Diagnostic objects.

Depending on the test runner configuration, the testing framework can 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.

Example: "My Custom Diagnostic"

Example: @dir

Examples

expand all

Create a test case for interactive testing.

testCase = matlab.unittest.TestCase.forInteractiveUse;

Test true.

verifyFalse(testCase,true)

Verification failed. --------------------- Framework Diagnostic: --------------------- verifyFalse failed. --> The value must evaluate to "false".

Actual Value:
  logical

   1
------------------
Stack Information:
------------------
In C:\work\TestLogicalFunctionsExample.m (TestLogicalFunctionsExample) at 12

Test false.

verifyFalse(testCase,false)

When you test using verifyFalse, the test fails if the actual value is not of type logical.

Create a test case for interactive testing.

testCase = matlab.unittest.TestCase.forInteractiveUse;

Test the value 0. The test fails because the value is of type double.

verifyFalse(testCase,0,"Value must be a logical scalar.")

Verification failed. ---------------- Test Diagnostic: ---------------- Value must be a logical scalar. --------------------- Framework Diagnostic: --------------------- verifyFalse failed. --> The value must be logical. It is of type "double".

Actual Value:
     0
------------------
Stack Information:
------------------
In C:\work\TestZeroExample.m (TestZeroExample) at 14

When you test using verifyFalse, the test fails if the actual value is nonscalar.

Create a test case for interactive testing.

testCase = matlab.unittest.TestCase.forInteractiveUse;

Test the value [false false]. The test fails because the value is nonscalar.

verifyFalse(testCase,[false false])

Verification failed. --------------------- Framework Diagnostic: --------------------- verifyFalse failed. --> The value must be scalar. It has a size of [1 2].

Actual Value:
  1×2 logical array

   0   0
------------------
Stack Information:
------------------
In C:\work\TestArrayOfLogicalValuesExample.m (TestArrayOfLogicalValuesExample) at 15

Tips

• verifyFalse is a convenience method. For example,verifyFalse(testCase,actual) is functionally equivalent to the following code.
  import matlab.unittest.constraints.IsFalse
  testCase.verifyThat(actual,IsFalse)
• Unlike verifyTrue, the verifyFalse method might create a new constraint for each call. For performance-critical tests, consider using verifyTrue.
• Use verification qualifications to produce and record failures without throwing an exception. Because 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 because 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 asIncomplete. 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 tests. A failure at the assertion point renders the current test asFailed 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 is so fundamental that continuing testing does not make sense. Fatal assertion qualifications are also useful when fixture teardown does not restore the environment state correctly, and aborting testing and starting a fresh session is preferable. For more information, see matlab.unittest.qualifications.FatalAssertable.

Version History

Introduced in R2013a