You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Mar 27, 2025. It is now read-only.
Copy file name to clipboardExpand all lines: CONFIGDOC.md
+5-7Lines changed: 5 additions & 7 deletions
Original file line number
Diff line number
Diff line change
@@ -498,17 +498,15 @@ Starting in R2024b, if you have a MATLAB Test™ license, you can view your
498
498
- Run tests with a [`matlab.buildtool.tasks.TestTask`](https://www.mathworks.com/help/matlab/ref/matlab.buildtool.tasks.testtask-class.html) instance using the **Run MATLAB Build** or `runMATLABBuild` step.
499
499
- Run tests with a default test runner using the **Run MATLAB Command** or `runMATLABCommand` step. A default test runner is equivalent to the runner that the testing framework configures by default when you call the [`runtests`](https://www.mathworks.com/help/matlab/ref/runtests.html) function.
500
500
501
-
After your tests run, the Jenkins build summary page displays the number of tests that ran as well as the number of passed, failed, and incomplete tests. You can click the **MATLAB Test Results** link on the page to access the table of test results. By default, the table includes a row for each test file that ran. Each row displays the status of a test file, its name, and the time it took to run. You can point to a filename in the table to view its parent directory.
501
+
After your tests run, the Jenkins build summary page displays the number of tests that ran as well as the number of passed, failed, and incomplete tests. You can click the **MATLAB Test Results** link on the page to access the table of test results. By default, the table includes a row for each test file that ran. The row displays the status of a test file, its name, and the time it took to run. You can point to a filename in the table to view its parent directory.
502
502
503
-

503
+

504
504
505
-
To view the tests within each test file, click the expander to the right of the filename. The test results are displayed in a table under the filename. The row corresponding to each test includes the test status (Passed, Failed, or Incomplete), test procedure name, test diagnostics, and duration.
505
+
You can interact with the table of test results. To view the tests within each test file, click the expander to the right of the filename. The test results are displayed in a table under the filename. The row corresponding to each test includes the test status (Passed, Failed, or Incomplete), test procedure name, test diagnostics, and duration.
506
506
507
-
- Each of the passed, failed, etc. buttons act as filters to respective type of tests
507
+

508
508
509
-

510
-
511
-
You can use the status filters above the **MATLAB Test Results** table to customize your view. For example, to focus on the failed tests, select the Failed status filter.
509
+
You can use the status filters above the **MATLAB Test Results** table to customize your view. For example, to focus on any incomplete tests, select the Incomplete status filter.
512
510
513
511
## Register MATLAB as Jenkins Tool
514
512
When you run MATLAB code and Simulink models as part of your automated pipeline of tasks, Jenkins invokes MATLAB as an external program. When you configure your project, you can explicitly specify the MATLAB version that Jenkins invokes by providing the path to the preferred MATLAB root folder. For example, you can use an `environment` block in your `Jenkinsfile` to specify a MATLAB root folder for your pipeline project.
0 commit comments