matlab.unittest.TestCase.addTeardown — Register a callback for test teardown.
addTeardown(testCase, callback, args...) records a function handle and its arguments in the active test context. The test executor invokes it during teardown.
Syntax
addTeardown(testCase, teardownFcn, input, ...)Inputs
testCase- Type
Any- Required
- Yes
- Default
- —
- Description
- TestCase or subclass in an active test lifecycle.
teardownFcn- Type
Any- Required
- Yes
- Default
- —
- Description
- Function handle invoked at teardown.
input- Type
Any- Required
- Variadic
- Default
- —
- Description
- Arguments retained for the teardown callback.
Returns
result- Type
Any- Description
- Empty double matrix; teardown registration is an effect.
Errors
RunMat:Testing:AddTeardown- When
- The callback or active lifecycle is invalid, or the command limit is reached.
- Message
A function handle and an active test lifecycle are required
Lifecycle and callback
Registration requires an active non-teardown test phase. The callback and arguments are retained for later execution; their effects cannot be statically bounded when the handle is unknown.
RunMat records a structured teardown command and a runtime invocation. User-function closures and method handles have not yet been fully qualified for capture and invocation parity across all execution targets; this contract remains partial.
Example
Reject teardown registration outside a test
testCase = matlab.unittest.TestCase();
addTeardown(testCase, @disp, 'done');Using matlab.unittest.TestCase.addTeardown with coding agents
Open a RunMat example with live inputs, then ask the agent to explain how matlab.unittest.TestCase.addTeardown changes the result.
Run a small matlab.unittest.TestCase.addTeardown example, explain the result, then change one input and compare the output.
Related Testing functions
Fixtures
matlab.unittest.fixtures.PathFixture · matlab.unittest.fixtures.TemporaryFolderFixture · matlab.unittest.TestCase.applyFixture
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
Plugins
matlab.unittest.plugins.CodeCoveragePlugin.forFolder · matlab.unittest.plugins.TestRunnerPlugin
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.verifyNotEmpty · matlab.unittest.TestCase.verifyNotEqual · matlab.unittest.TestCase.verifyThat · matlab.unittest.TestCase.verifyTrue
Source you can read
Every RunMat function's source is public. Read exactly how matlab.unittest.TestCase.addTeardown is executed, line by line, in Rust.
- View the source for matlab.unittest.TestCase.addTeardown 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.