Skip to content
This repository was archived by the owner on Mar 27, 2025. It is now read-only.

Commit 307a81e

Browse files
committed
Updated review comments #1
1 parent 2de4b19 commit 307a81e

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

README.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,9 @@ Enter the value returned by “matlabroot” in the field named “MATLAB root
1818
![new_enter_matlabroot](https://user-images.githubusercontent.com/47204011/55624374-45097e00-57c3-11e9-96e1-5fa0fc966767.png)
1919

2020
#### Configuring “Automatic” Option
21-
This option finds tests written using the MATLAB unit testing framework and/or Simulink Test and runs them. If the code is organized using projects, it will locate all test files in the project that have been classified as "Test". If the code does not leverage projects or uses a MATLAB version prior to R2019a, the plugin will discover all tests in the current Jenkins workspace including subfolders. When using "Automatic" option, It is mandatory for user to make sure that, appropriate SCM configuration is done before build step execution, which pulls the latest code from SCM into the Jenkins workspace. If SCM is not used to maintain the code then, user should make sure to add appropriate script, as part of build step before MATLAB plugin to copy the code in Jenkins workspace.
21+
This option finds tests written using the MATLAB unit testing framework and/or Simulink Test and runs them. If the code is organized using projects, it will locate all test files in the project that have been classified as "Test". If the code does not leverage projects or uses a MATLAB version prior to R2019a, the plugin will discover all tests in the current Jenkins workspace including subfolders.
22+
23+
If you are using source code management (SCM) system, like Git, then the job must include an appropriate SCM configuration to checkout the code before running the MATLAB plugin. If you are not using any SCM system to manage your code, then a previous build step should make sure the code is available in the workspace before running the MATLAB plugin.
2224

2325
The automatic test running feature enables you to generate different types of test artifacts. They could be used with other Jenkins plugins as part of a post-build action to publish the test results. To configure the Jenkins build for running MATLAB tests automatically, follow these steps.
2426

0 commit comments

Comments
 (0)