uft
uft/uft@v1
Process 'uft' function.
If the function is used more than once in a job, it is up to the caller to ensure no previous test execution results remain before executing a new test.
It is also up to the caller to attach the relevant reports so that
publishers can do their job too, by using the actions/get-files@v1
function or some other means.
Test parameters are optional but if used they must be declared in the test run.
Example
- uses: uft/uft@v1
with:
datasource: uftSolution/uftTestFolder
test_parameters:
param1: value
param2: value
Inputs
The function has the following inputs:
-
datasource
(required)The datasource to use.
-
test_parameters
(optional)External parameters to use.
Reports
The function generates the following reports:
(* is a wildcard matching any character string.)
-
*uft-results.xml
Surefire (XML).
-
*uft-report.tar
TAR archive.
Contains all files present in the
Res1
results folder.
uft/execute@v1
An 'execute' function for use by generators.
execute
function has a mandatory test
input.
Example
- uses: uft/execute@v1
with:
test: uftSolution/uftTestFolder
Inputs
The function has the following inputs:
-
test
(required)The datasource to use.
Reports
The function generates the following reports:
(* is a wildcard matching any character string.)
-
*uft-results.xml
Surefire (XML).
-
*uft-report.tar
TAR archive.
Contains all files present in the
Res1
results folder.
uft/params@v1
A 'params' function for use by generators.
params
function has mandatory data
and format
inputs.
Example
- uses: uft/params@v1
with:
data:
global:
key1: value1
key2: value2
test:
key1: value3
key3: value4
format: format
format
must so far be SQUASHTM_FORMAT (tm.squashtest.org/params@v1
).
data
can have two keys:
global
for defining global parameters.test
for defining test parameters.
Inputs
The function has the following inputs:
-
data
(required)The data to use for the automated test.
-
format
(required)The format to use for the automated test data.
actions/prepare-inception@v1
Preload the inception environment with data.
prepare-inception
function has a mandatory input per file it
prepares.
In the case of UFT:
Example
- uses: actions/prepare-inception@v1
with:
uft-results.xml: ${{ resources.files.xml }}
uft-report.tar: ${{ resources.files.tar }}
Inputs
The function has the following inputs:
-
uft-results.xml
(required)Surefire (XML), this report is the one used to determinate the test status (success/failure).
-
uft-report.tar
(optional)TAR archive.