SpecSync Documentation
Jira
Jira
  • Introduction to SpecSync for Jira
  • Getting started
    • Getting started using SpecFlow
    • Getting started using Cucumber or other Gherkin-based BDD tool
  • Installation & Setup
    • Install as .NET tool
    • Install as .NET Console App
    • Install as native binaries for Linux or macOS
    • Install as Docker image
    • Setup and Configure
  • Features
    • Push features
      • Pushing scenario changes to Test Cases
      • Configuring the format of the synchronized test cases
      • Synchronizing Scenario Outlines
      • Update Test Case fields
      • Attach files to Test Cases using tags
      • Customization: Setting Test Case fields with default values
      • Customization: Update custom Test Case fields on push
      • Customization: Ignoring marked Test Case steps
      • Customization: Ignoring Test Case Tags
      • Customization: Ignore non-supported local tags
      • Customization: Mapping tags
      • Customization: Synchronizing scenarios from feature branches
      • Customization: Automatically link changed Test Cases
      • Customization: Synchronize linked artifact titles
      • Customization: Do not synchronize title
    • Pull features
      • Pulling Test Case changes to local scenarios
    • Common synchronization features
      • Configuration key
      • Remote scope
      • Linking Work Items using tags
      • Synchronizing Test Case hierarchies
      • Excluding scenarios from synchronization
      • Synchronization conflict resolution
    • Test result publishing features
      • Publishing test result files
    • General features
      • Jira authentication options
      • Configuration file
      • Hierarchical configuration files
      • Local test case conditions
      • Configuration wizards
      • SpecSync plugins
    • Customizations
    • Plugin list
  • Licensing
  • Guides
    • What is my Jira server URL?
    • Jira Test Case Management (TCM) solution
    • How to define the local feature-set to be synchronized
    • Filters and scopes
    • How to use SpecSync from build or release pipeline
    • How to upgrade to a newer version of SpecSync
    • How to attach files to test results
    • Using SpecSync with Cucumber
    • Using SpecSync with Cypress
    • Using SpecSync with Postman
    • Using SpecSync with TestNG
    • Using SpecSync on macOS or Linux
    • Using SpecSync inside a Docker container
    • Migrating from SpecSync v1 to v5
  • Changelog
  • Release Model and Roadmap
  • Downloads
  • Reference
    • Command line reference
      • init
      • upgrade
      • push
      • pull
      • publish-test-results
      • version
    • Configuration reference
      • toolSettings
      • local
      • remote
      • jira
      • knownRemotes
      • synchronization
        • push
        • pull
        • links
        • attachments
        • format
        • fieldUpdates
      • hierarchies
      • publishTestResults
      • specFlow
      • customizations
    • Compatibility
    • Older versions
  • Contact
    • SpecSync Support
    • Troubleshooting
    • FAQ
  • Project Website
Powered by GitBook
On this page
  • Settings
  • Setting Placeholders

Was this helpful?

  1. Reference
  2. Configuration reference

publishTestResults

PrevioushierarchiesNextspecFlow

Last updated 2 months ago

Was this helpful?

This configuration section contains settings related to publishing test results.

To read more about publishing test results see the page. Please also check the 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

publishEmptyResults

Publishes test results even if no matching results found.

false

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)

testResult/fileFormat — The format of the test result file. Please check the page for supported formats. Invoking the publish-test-result command with ? as format as command line option will list all supported format as well.

specified as

Specifies additional settings for the created test run. The value can contain .

Specifies additional settings for the created test results. The value can contain .

Publishing test result files
command line reference
Configuration reference
publish-test-results
command line option
placeholders
placeholders
Compatibility