|
2 | 2 |
|
3 | 3 | The Jenkins plugin for MATLAB® enables you to easily run your MATLAB and Simulink® tests and generate artifacts such as *JUnit* and *TAP* test results, and *Cobertura* code or model coverage reports. You can also export your Simulink Test™ Manager results. This guide shows you examples of how to configure the plugin for different objectives, considering a Microsoft® Windows® platform. |
4 | 4 |
|
5 | | -## Configure Plugin for Freestyle Project |
6 | | -To configure the plugin for a freestyle project, select **Run MATLAB Tests** from the **Add build step** list. Then, enter the value returned by the **matlabroot** function in the **MATLAB root** field. |
| 5 | +## Documentation |
7 | 6 |
|
8 | | -  |
9 | | - |
10 | | -  |
11 | | - |
12 | | -### Option 1: Freestyle Project with Automatic Test Mode |
13 | | -With the Jenkins plugin for MATLAB, you have the option to run your tests in either *automatic* or *custom* mode. The automatic test mode employs a default setting to run tests written using the MATLAB Unit Testing Framework and/or Simulink Test. If your source code is organized as files and folders within a project, the plugin will consider any test files in the project that have been tagged as **Test**. If your code does not leverage a project or uses a MATLAB version prior to R2019a, the plugin will consider all tests in the current Jenkins workspace including the subfolders. |
| 7 | +#### Configuration Steps |
| 8 | +* To learn how to configure the Jenkins Plugin for MATLAB, see the [plugin configuration guide.](/CONFIGDOC.md) |
14 | 9 |
|
15 | | -If you use a source code management (SCM) system such as Git, then your job must include the appropriate SCM configuration to check out the code before it can invoke the MATLAB plugin. If you do not use any SCM systems to manage your code, then an additional build step is required to ensure that the code is available in the Jenkins workspace before the build starts. |
16 | | - |
17 | | -The automatic test execution feature of the plugin enables you to generate different types of test artifacts. To publish the test results, you can use these artifacts with other Jenkins plugins. To configure the Jenkins build where MATLAB tests run automatically, follow these steps. |
18 | | - |
19 | | -1) From the **Test mode** drop-down list, select the **Automatic** option (**Automatic** is the default testing mode). |
20 | | - |
21 | | -  |
22 | | - |
23 | | -2) Select your desired test artifacts. |
24 | | - |
25 | | -  |
26 | | - |
27 | | - The selected artifacts will be saved in the **matlabTestArtifacts** folder of the Jenkins workspace. |
28 | | - |
29 | | -  |
30 | | - |
31 | | -  |
32 | | - |
33 | | - If you do not select any of the test artifact check boxes, the **matlabTestArtifacts** folder will not be created in the workspace. However, tests will still run and potential test failures will fail the build. |
34 | | - |
35 | | - The **Automatic** test mode results in a MATLAB script file named **runMatlabTests.m** in the Jenkins workspace. The plugin uses this file to run the tests and generate the test artifacts. You can review the contents of the script to understand the testing workflow. |
36 | | - |
37 | | -  |
38 | | - |
39 | | -### Option 2: Freestyle Project with Custom Test Mode |
40 | | -This option enables you to develop your custom MATLAB commands for running tests. To configure the Jenkins build where you can customize the MATLAB test execution, follow these steps. |
41 | | - |
42 | | -1) From the **Test mode** drop-down list, select the **Custom** option. |
43 | | - |
44 | | -  |
45 | | - |
46 | | -2) Enter your commands in the **MATLAB command** field. If you specify more than one MATLAB command, use a comma or semicolon to separate the commands. The build will fail if the execution of any command results in an error. |
47 | | - |
48 | | -  |
49 | | - |
50 | | - **Note:** If you need several MATLAB commands to run your tests, consider writing a MATLAB script or function as part of your repository and executing this script or function instead. Test artifacts are not autogenerated if you choose to run tests using custom MATLAB commands. You can generate your desired test artifacts by configuring the test runner in the script or function that you invoke from the **MATLAB command** field. |
51 | | - |
52 | | -  |
53 | | - |
54 | | -## Configure Plugin for Multi-Configuration Project |
55 | | -In addition to freestyle projects, the Jenkins plugin for MATLAB supports [multi-configuration (matrix) projects](https://wiki.jenkins.io/display/JENKINS/Building+a+matrix+project). Multi-configuration projects are useful when builds include similar steps, for example when the same test suite should run on different platforms (e.g., Windows, Linux, and Mac) or using several MATLAB versions. |
56 | | - |
57 | | - |
58 | | - |
59 | | -As in a freestyle project, you can run your tests in automatic or custom mode within a multi-configuration project. The configuration requires you to specify the location where MATLAB is installed as well as the test execution mode. You should also add user-defined axes in the **Configuration Matrix** to specify the duplicating build steps. |
60 | | - |
61 | | -### Option 1: Multi-Configuration Project with Automatic Test Mode |
62 | | - |
63 | | -To configure the plugin for a matrix build where tests run automatically in multiple MATLAB versions, create a multi-configuration project and follow these steps. |
64 | | - |
65 | | -1) Add a user-defined axis in the **Configuration Matrix** to represent the MATLAB versions in the build. Specify the name of the axis in the **Name** field and its values in the **Values** field. Separate the elements in the **Values** field with a space. In this example, four MATLAB versions are specified, which will be used to run the same set of tests. |
66 | | - |
67 | | - |
68 | | - |
69 | | -2) In the **Run MATLAB Tests** section of the project, include the user-defined axis name in the **MATLAB root** field to specify the locations where MATLAB is installed. In this example, **$VERSION** will be replaced by one axis value per build step. |
70 | | - |
71 | | - |
72 | | - |
73 | | -You can select the test artifact check boxes when tests run automatically. Once you have made your selections, save your settings and run the build. |
74 | | - |
75 | | -### Option 2: Multi-Configuration Project with Custom Test Mode |
76 | | - |
77 | | -To configure the matrix build where you can customize the MATLAB test execution, create a multi-configuration project and follow these steps. |
78 | | - |
79 | | -1) Add a user-defined axis in the **Configuration Matrix** to represent the MATLAB versions in the build. |
80 | | - |
81 | | - |
82 | | - |
83 | | -2) Add another user-defined axis using the **Add axis** button. In this example, the **TEST_TAG** axis specifies the possible test tags for a group of test elements. |
84 | | - |
85 | | - |
86 | | - |
87 | | -3) In the **Run MATLAB Tests** section of the project, use the **VERSION** axis to specify the locations where MATLAB is installed. |
88 | | - |
89 | | - |
90 | | - |
91 | | -4) From the **Test mode** drop-down list, select the **Custom** option. Use the second user-defined axis to create your commands and enter them in the **MATLAB command** field. Then, save your settings and run the build. |
92 | | - |
93 | | - |
94 | | - |
95 | | -**Notes:** |
96 | | -1) For a user-defined axis named **VAR**, **$VAR** and **${VAR}** are both valid formats for accessing the values. |
97 | | - |
98 | | -2) A multi-configuration project creates a separate workspace for each user-defined axis value. If you specify the full paths to where MATLAB is installed as axis values, Jenkins fails to create separate workspaces and fails the build. |
| 10 | +#### Change Log |
99 | 11 |
|
| 12 | +* For a detailed list of releases, see [Change logs](/CHANGELOG.md). |
100 | 13 |
|
101 | 14 | ## Contact Us |
102 | 15 | If you have any questions or suggestions, please contact MathWorks. |
|
0 commit comments