src/main/resources/com/microfocus/application/automation/tools/octane/actions/UFTTestDetectionPublisher/help.html
<!--
~ Certain versions of software accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company.
~ This software was acquired by Micro Focus on September 1, 2017, and is now offered by OpenText.
~ Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.
~ __________________________________________________________________
~ MIT License
~
~ Copyright 2012-2024 Open Text
~
~ The only warranties for products and services of Open Text and
~ its affiliates and licensors ("Open Text") are as may be set forth
~ in the express warranty statements accompanying such products and services.
~ Nothing herein should be construed as constituting an additional warranty.
~ Open Text shall not be liable for technical or editorial errors or
~ omissions contained herein. The information contained herein is subject
~ to change without notice.
~
~ Except as specifically indicated otherwise, this document contains
~ confidential information and a valid license is required for possession,
~ use or copying. If this work is provided to the U.S. Government,
~ consistent with FAR 12.211 and 12.212, Commercial Computer Software,
~ Computer Software Documentation, and Technical Data for Commercial Items are
~ licensed to the U.S. Government under vendor's standard commercial license.
~
~ Unless required by applicable law or agreed to in writing, software
~ distributed under the License is distributed on an "AS IS" BASIS,
~ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
~ See the License for the specific language governing permissions and
~ limitations under the License.
~ ___________________________________________________________________
-->
<div>
This build step discovers UFT tests and external data table in the SCM repository and synchronizes corresponding entities to ALM Octane.</br>
Discovery can done in two ways
<ul>
<li>Full sync - Cloned SCM repository is scanned and all found tests and data tables are synchronized to ALM Octane.</li>
<li>ChangeSet sync - Only commits that are related to the build are scanned and only affected entities are synchronized.</li>
</ul>
By default, full sync is done for the first run of the job, and after that only ChangeSet sync is done.
If you need to force full sync - define in the job a boolean parameter "Full sync" and execute the job with this parameter is checked.
</br>
If you need to assign a discovered test in ALM Octane to a specific test runner, define a string parameter "Test Runner ID" and assign to it the ID of the relevant test runner.
</div>