MATLAB Build Tool: Run tests impacted since source control revision
Run only the tests impacted by changes since a specified Git™ revision by using the BaseRevision property or task
argument of a matlab.buildtool.tasks.TestTask instance. For example, you can configure a task
to run the tests impacted by changes to code and data in your repository since the last
commit or push. For more information, see Run Impacted Tests in Git Repository.
MATLAB Build Tool: Produce code coverage results for generated C/C++ code in equivalence tests
Produce code coverage results for generated C/C++ code in your equivalence tests by
creating a built-in task from the matlab.buildtool.tasks.TestTask class in your build file. To produce the
generated code coverage results, use the new
GeneratedCodeCoverageResults property or
addGeneratedCodeCoverage method of the task. For an example, see Produce Coverage Results for Generated Code in Equivalence Tests.
Export test data for inspection when no baseline exists
When running a baseline test without a baseline, you can export the recorded test data
to the workspace by clicking the Export test data to workspace link in
the test diagnostics. The testing framework exports the test data as a variable named
actual. After inspecting the exported data, you can approve it as
baseline data by clicking the Create baseline from recorded test data
link in the test diagnostics.
In previous releases, when you use baseline-specific qualification methods, such as
verifyEqualsBaseline or the matlabtest.constraints.EqualsBaseline constraint, the Export test data
to workspace link appears in the test diagnostics only if baseline data already
exists. For more information about baseline testing, see Create Baseline Tests for MATLAB Code.
Rerun tests from previous runs in the MATLAB Test Manager
In the MATLAB Test Manager, you can rerun tests that you executed in a
previous run. To rerun the tests, open the run in the MATLAB Test Manager and
click the Run button 
. Running tests from previous runs uses the latest test code
in your test files.
Filter tests for additional test types
In the MATLAB Test Manager, you can now filter for these additional test types:
App
Mock
Performance
Parameterized
Create justifications for missing coverage in generated code
You can now create justifications for blocks of code that are missing coverage in generated code from the statement, function, and decision views of the code coverage report. You cannot create justifications from the condition or modified condition/decision coverage (MC/DC) views. For more information about how to create justifications, see Create Justification to Filter Code Block.
Specify functions to build using function names or handles
When using the build method
of the matlabtest.compiler.TestCase class, you can now specify the
MATLAB® functions to build by using function names or function handles. Prior to
R2026a, you had to specify these functions by using filenames.
LLM for generating tests using MATLAB Copilot upgraded to GPT-5 mini
The Generate Test MATLAB Copilot action now uses the GPT-5 mini model as the underlying LLM.
Functionality being removed or changed
Find tests that depend on the current file in the MATLAB Editor
Behavior change
Starting in R2026a, when you find tests for the current file, and the current file is in a project, the MATLAB Editor searches the project for dependent tests and opens them. When you find tests for a file that is not in a project, you must specify the folder in which to search for the dependent tests.
Prior to R2026a, if the current file was in a project, you had to specify the folder in which to search for dependent tests.
For more information, see Find Tests That Depend on Current File in the MATLAB Editor.
Save HTML test report and supporting files in a single file
Behavior change
When you generate an HTML test report, the MATLAB Test Manager saves the report as a single HTML file. Prior to R2026a, the MATLAB Test Manager saves the HTML test report in a folder in multiple files.