uft

uft/uft@v1

Process 'uft' action.

If the action is used more than once in a job, it is up to the caller to ensure no previous test execution results remains 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 action 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

• datasource (required)

  The datasource to use.

• test_parameters (optional)

  External parameters to use.

uft/execute@v1

An 'execute' action for use by generators.

execute actions have a mandatory test input.

Example

- uses: uft/execute@v1
  with:
    test: uftSolution/uftTestFolder

Inputs

• test (required)

  The datasource to use.

uft/params@v1

A 'params' action for use by generators.

params actions have 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

• data (required)

  The data to use for the automated test.

• format (required)

  The format to use for the automated test data.