|
1 | 1 | description: >
|
2 |
| - Run all tests in a MATLAB project and generate test artifacts. MATLAB includes any files in your |
3 |
| - project that have a Test label. If your pipeline does not leverage a MATLAB project, then MATLAB |
4 |
| - includes all tests in the the root of your repository including its subfolders. |
| 2 | + Run MATLAB and Simulink tests and generate artifacts. By default, the command includes any files |
| 3 | + in your project that have a `Test` label. If your pipeline does not use a MATLAB project, or if |
| 4 | + it uses a MATLAB release before R2019a, then the command includes all tests in the root of your |
| 5 | + repository and in any of its subfolders. The command fails if any of the included tests fails. |
5 | 6 |
|
6 | 7 | parameters:
|
7 |
| - test-results-junit: |
| 8 | + source-folder: |
8 | 9 | description: >
|
9 |
| - Path to write test results report in JUnit XML format. |
| 10 | + Location of the folder containing source code, relative to the project root folder. The |
| 11 | + specified folder and its subfolders are added to the top of the MATLAB search path. If |
| 12 | + you specify `source-folder` and then generate a coverage report, MATLAB uses only the source |
| 13 | + code in the specified folder and its subfolders to generate the report. You can specify multiple |
| 14 | + folders using a colon-separated or semicolon-separated list. |
10 | 15 | type: string
|
11 | 16 | default: ''
|
12 |
| - code-coverage-cobertura: |
| 17 | + select-by-folder: |
13 | 18 | description: >
|
14 |
| - Path to write code coverage report in Cobertura XML format. |
| 19 | + Location of the folder used to select test suite elements, relative to the project root folder. |
| 20 | + To create a test suite, MATLAB uses only the tests in the specified folder and its subfolders. |
| 21 | + You can specify multiple folders using a colon-separated or semicolon-separated list. |
15 | 22 | type: string
|
16 | 23 | default: ''
|
17 |
| - code-coverage-html: |
| 24 | + select-by-tag: |
18 | 25 | description: >
|
19 |
| - Path to write code coverage report in HTML format. |
| 26 | + Test tag used to select test suite elements. To create a test suite, MATLAB uses only the test elements |
| 27 | + with the specified tag. |
20 | 28 | type: string
|
21 | 29 | default: ''
|
22 |
| - source-folder: |
| 30 | + strict: |
23 | 31 | description: >
|
24 |
| - Location of the folder containing source code, relative to the project root folder. The |
25 |
| - specified folder and its subfolders are added to the top of the MATLAB search path. To |
26 |
| - generate a code coverage report, MATLAB uses only the source code in the specified folder and |
27 |
| - its subfolders. You can specify multiple folders using a colon-separated or a |
28 |
| - semicolon-separated list. |
29 |
| - type: string |
30 |
| - default: '' |
31 |
| - select-by-folder: |
| 32 | + Option to apply strict checks when running tests, specified as `false` or `true`. If you specify |
| 33 | + a value of `true`, the command generates a qualification failure whenever a test issues a warning. |
| 34 | + type: boolean |
| 35 | + default: false |
| 36 | + use-parallel: |
32 | 37 | description: >
|
33 |
| - Location of the folder used to select test suite elements, relative to the project root folder. |
34 |
| - To generate a test suite, MATLAB uses only the tests in the specified folder and its subfolders. |
35 |
| - You can specify multiple folders using a colon-separated or a semicolon-separated list. |
| 38 | + Option to run tests in parallel, specified as `false` or `true`. If the test runner configuration |
| 39 | + is suited for parallelization, you can specify a value of `true` to run tests in parallel. This |
| 40 | + parameter requires a Parallel Computing Toolbox license. |
| 41 | + type: boolean |
| 42 | + default: false |
| 43 | + output-detail: |
| 44 | + description: > |
| 45 | + Amount of event detail displayed for the test run, specified as `none`, `terse`, `concise`, `detailed`, |
| 46 | + or `verbose`. By default, the command displays failing and logged events at the `detailed` level and test |
| 47 | + run progress at the `concise` level. |
36 | 48 | type: string
|
37 | 49 | default: ''
|
38 |
| - select-by-tag: |
| 50 | + logging-level: |
39 | 51 | description: >
|
40 |
| - Test tag used to select test suite elements. To generate a test suite, MATLAB uses only the test elements |
41 |
| - with the specified tag. |
| 52 | + Maximum verbosity level for logged diagnostics included for the test run, specified as `none`, `terse`, |
| 53 | + `concise`, `detailed`, or `verbose`. By default, the command includes diagnostics logged at the `terse` level. |
42 | 54 | type: string
|
43 | 55 | default: ''
|
44 |
| - model-coverage-cobertura: |
| 56 | + test-results-pdf: |
45 | 57 | description: >
|
46 |
| - Path to write model coverage report in Cobertura XML format. |
| 58 | + Path to write the test results in PDF format. On macOS platforms, this parameter is supported in MATLAB R2020b and later. |
47 | 59 | type: string
|
48 | 60 | default: ''
|
49 |
| - model-coverage-html: |
| 61 | + test-results-junit: |
50 | 62 | description: >
|
51 |
| - Path to write model coverage report in HTML format. |
| 63 | + Path to write the test results in JUnit-style XML format. |
52 | 64 | type: string
|
53 | 65 | default: ''
|
54 | 66 | test-results-simulink-test:
|
55 | 67 | description: >
|
56 |
| - Path to export Simulink Test Manager results in MLDATX format. |
| 68 | + Path to export Simulink Test Manager results in MLDATX format. This parameter requires a Simulink Test license, and |
| 69 | + is supported in MATLAB R2019a and later. |
57 | 70 | type: string
|
58 | 71 | default: ''
|
59 | 72 | test-results-html:
|
60 | 73 | description: >
|
61 |
| - Path to write test results report in HTML format. |
| 74 | + Path to write the test results in HTML format. |
62 | 75 | type: string
|
63 | 76 | default: ''
|
64 |
| - test-results-pdf: |
| 77 | + code-coverage-cobertura: |
65 | 78 | description: >
|
66 |
| - Path to write test results report in PDF format. |
| 79 | + Path to write the code coverage results in Cobertura XML format. |
67 | 80 | type: string
|
68 | 81 | default: ''
|
69 |
| - no-output-timeout: |
| 82 | + code-coverage-html: |
70 | 83 | description: >
|
71 |
| - Elapsed time the tests can run without output. The string is a decimal with unit suffix, |
72 |
| - such as “20m”, “1.25h”, “5s”. The default is 10 minutes and the maximum is governed by the |
73 |
| - maximum time a job is allowed to run. |
| 84 | + Path to write the code coverage results in HTML format. |
74 | 85 | type: string
|
75 |
| - default: 10m |
76 |
| - strict: |
77 |
| - description: > |
78 |
| - Whether to apply strict checks when running the tests. For example, the command generates a |
79 |
| - qualification failure if a test issues a warning. |
80 |
| - type: boolean |
81 |
| - default: false |
82 |
| - use-parallel: |
83 |
| - description: > |
84 |
| - Whether to run tests in parallel (requires Parallel Computing Toolbox). This feature might |
85 |
| - not be compatible with certain arguments, in which case, tests run in serial regardless of |
86 |
| - the specified value. |
87 |
| - type: boolean |
88 |
| - default: false |
89 |
| - output-detail: |
| 86 | + default: '' |
| 87 | + model-coverage-cobertura: |
90 | 88 | description: >
|
91 |
| - Display level for event details produced by the test run, specified as 'None', 'Terse', 'Concise', 'Detailed', or 'Verbose'. |
| 89 | + Path to write the model coverage results in Cobertura XML format. This parameter requires a Simulink Coverage license, |
| 90 | + and is supported in MATLAB R2018b and later. |
92 | 91 | type: string
|
93 | 92 | default: ''
|
94 |
| - logging-level: |
| 93 | + model-coverage-html: |
95 | 94 | description: >
|
96 |
| - Maximum verbosity level for logged diagnostics included for the test run, specified as 'None', 'Terse', 'Concise', 'Detailed', or 'Verbose'. |
| 95 | + Path to write the model coverage results in HTML format. This parameter requires a Simulink Coverage license, and is |
| 96 | + supported in MATLAB R2018b and later. |
97 | 97 | type: string
|
98 | 98 | default: ''
|
| 99 | + no-output-timeout: |
| 100 | + description: > |
| 101 | + Elapsed time the tests can run without output. The string is a decimal with unit suffix, |
| 102 | + such as “20m”, “1.25h”, “5s”. The default is 10 minutes and the maximum is governed by the |
| 103 | + maximum time a job is allowed to run. |
| 104 | + type: string |
| 105 | + default: 10m |
99 | 106 | startup-options:
|
100 | 107 | description: >
|
101 |
| - MATLAB startup options. If you specify more than one option, use a space to |
102 |
| - separate the options. |
| 108 | + MATLAB startup options, specified as a list of options separated by spaces. For more |
| 109 | + information about startup options, see |
| 110 | + https://www.mathworks.com/help/matlab/matlab_env/commonly-used-startup-options.html. |
103 | 111 | type: string
|
104 | 112 | default: ""
|
105 | 113 |
|
|
0 commit comments