publishTestResults

This configuration section contains settings related to publishing test results.

To read more about publishing test results see the Publishing test result files page. Please also check the command line reference for the publish-test-results command.

The following example shows the most common options within this section.

{
  ...
  "publishTestResults": {
    "testResult": {
      "filePath": "test-result.trx"
    },
    "treatInconclusiveAs": "Failed",
    "testRunSettings": {
      "description": "Acceptance test results",
      "folder": "/BDD"
    },
    "testResultSettings": {
      "environment": "Staging"
    }
  },
  ...
}

Settings

Setting
Description
Default

testResult

The test result configuration

  • testResult/filePath — The path of the test result file (e.g. TRX) file or a folder containing multiple test result files.

treatInconclusiveAs

Maps the Inconclusive test results. Some test execution frameworks report skipped scenarios as Inconclusive, so they should be mapped to another value, e.g. NotExecuted.

not mapped

testRunSettings

  • testRunSettings/name — In Zephyr Scale, it sets the Test Cycle name

  • testRunSettings/description — In Zephyr Scale, it sets the Test Cycle description

  • testRunSettings/iteration — In Zephyr Scale, it sets the Test Cycle iteration

  • testRunSettings/folder — In Zephyr Scale, it sets the Test Cycle folder

  • testRunSettings/version — In Zephyr Scale, it sets the Test Cycle version

use default settings

testResultSettings

  • testResultSettings/comment — In Zephyr Scale, it sets the test result comment

  • testResultSettings/environment — In Zephyr Scale, it sets the test result environment

  • testResultSettings/iteration — In Zephyr Scale, it sets the test result iteration

  • testResultSettings/version — In Zephyr Scale, it sets the test result version

use default settings

Setting Placeholders

Placeholder
Description

{br}

a new line

{env:ENVIRONMENT_VARIABLE_NAME}

The content of the environment variable specified (ENVIRONMENT_VARIABLE_NAME in this example)

Last updated