matlab.unittest.TestCase.verifyNotEmpty — Verify that a value has at least one element.
verifyNotEmpty(testCase, actual) checks whether the runtime value has a nonzero element count.
Syntax
verifyNotEmpty(testCase, actual, diagnostic...)Inputs
testCase- Type
Any- Required
- Yes
- Default
- —
- Description
- A TestCase object or subclass.
actual- Type
Any- Required
- Yes
- Default
- —
- Description
- Value being qualified.
diagnostic- Type
Any- Required
- Variadic
- Default
- —
- Description
- Optional diagnostics; the first scalar text or Diagnostic message replaces the default failure text.
Returns
result- Type
Any- Description
- Empty double matrix on success; failures stop or filter the current test.
Errors
RunMat:Testing:InvalidTestCase- When
- The receiver is not a TestCase object or subclass.
- Message
first argument must be a matlab.unittest.TestCase
RunMat:Test:VerificationFailed- When
- A verification fails outside an active test; inside an active test, its diagnostic is recorded and execution continues.
- Message
verification failed
Element-count check
The current implementation checks the value's element count and may request runtime shape information. It does not make a class-specific assertion about the value.
Verification lifecycle
In an active test, a failed verification records a diagnostic and returns an empty double matrix so that the test continues. Outside an active test, a failed verification returns RunMat:Test:VerificationFailed. Passing calls also return an empty double matrix. Optional diagnostics currently use only the first scalar text or Diagnostic object's Message.
Example
Verify an array contains an element
testCase = matlab.unittest.TestCase();
result = verifyNotEmpty(testCase, [1]);Using matlab.unittest.TestCase.verifyNotEmpty with coding agents
Open a RunMat example with live inputs, then ask the agent to explain how matlab.unittest.TestCase.verifyNotEmpty changes the result.
Run a small matlab.unittest.TestCase.verifyNotEmpty example, explain the result, then change one input and compare the output.
Related Testing functions
Qualifications
matlab.unittest.TestCase.assertEqual · matlab.unittest.TestCase.assertThat · matlab.unittest.TestCase.assertTrue · matlab.unittest.TestCase.assumeEqual · matlab.unittest.TestCase.assumeTrue · matlab.unittest.TestCase.fatalAssertTrue · matlab.unittest.TestCase.verifyEmpty · matlab.unittest.TestCase.verifyEqual · matlab.unittest.TestCase.verifyFalse · matlab.unittest.TestCase.verifyGreaterThan · matlab.unittest.TestCase.verifyLessThan · matlab.unittest.TestCase.verifyNotEqual · matlab.unittest.TestCase.verifyThat · matlab.unittest.TestCase.verifyTrue
Testing
functiontests · matlab.unittest.TestCase · matlab.unittest.TestRunner.addPlugin · matlab.unittest.TestRunner.run · matlab.unittest.TestRunner.withTextOutput · testsuite
Constraints
matlab.unittest.constraints.IsEqualTo · matlab.unittest.constraints.IsFalse · matlab.unittest.constraints.IsTrue
Source you can read
Every RunMat function's source is public. Read exactly how matlab.unittest.TestCase.verifyNotEmpty is executed, line by line, in Rust.
- View the source for matlab.unittest.TestCase.verifyNotEmpty in Rust on GitHub
- Learn how the RunMat runtime works
- Found a bug? Open an issue with a minimal reproduction.
About RunMat
RunMat is a runtime that executes MATLAB-syntax code fast on any GPU. The runtime is free for individuals, including freelancers; students and faculty at an academic institution, for teaching or research there; contributors to an open-source project, for work on that project; organizations with 250 or fewer people and US$10M or less in annual revenue; and anyone, for non-production use. See runmat.com/license.
- RunMat automatically optimizes your math for GPU execution on Apple, Nvidia, and AMD hardware. No code changes needed. Simulations that took hours now take minutes.
- Start running code in seconds. RunMat runs in the browser, on the desktop, or from the CLI. No license server, no IT ticket.