> User Documentation Home

User Handbook
Tutorials
Resources

The following plugin provides functionality available through Pipeline-compatible steps. Read more about how to integrate steps into your Pipeline in the Steps section of the Pipeline Syntax page.

For a list of other such plugins, see the Pipeline Steps Reference page.

Zephyr Scale

View this plugin on the Plugins site

downloadFeatureFiles: Zephyr Scale: Download Feature Files

Downloads feature files from Zephyr Scale.
  • serverAddress
    One of the preconfigured Jira instances. If you do not have any, please go to General Configuration and set up a new Jira instance.
    • Type: String
  • projectKey
    Jira project key to filter test cases.
    • Type: String
  • targetPath
    The path where the downloaded feature files will be placed.
    • Type: String

publishTestResults: Zephyr Scale: Publish Test Results

Automatically publishes automated test results to Zephyr Scale.
  • serverAddress
    One of the preconfigured Jira instances. If you do not have any, please go to General Configuration and set up a new Jira instance.
    • Type: String
  • projectKey
    Jira project key to publish the test results to.
    • Type: String
  • filePath
    The path where the build places generated test result files. You can also use Ant style patterns such as **/test-reports/*.json.
    • Type: String
  • autoCreateTestCases
    When this option is checked, test cases with no KEY annotation will be automatically created, if there are no test cases matching their names.
    • Type: boolean
  • format
    Choose the test framework where the test results will be generated from.
    • Type: String
  • customTestCycle
    Zephyr Scale Cloud only. If sent to Zephyr Scale Server/DC, the values will be ignored.

    Use this section to customize the test cycle that will be created with the test results.

    All fields are optional.

    If not used, the test cycle will be named Automated Build and will be placed at the root folder of your test cycle library. All other fields will be empty.

    Please note that if you use this section and have required test cycle custom fields in your project, you'll have to set the custom field values.
      Nested Object
    • name
      • Type: String
    • description
      • Type: String
    • jiraProjectVersion
      • Type: String
    • folderId
      • Type: String
    • customFields
      • Type: String

Was this page helpful?

Please submit your feedback about this page through this quick form.

Alternatively, if you don't wish to complete the quick form, you can simply indicate if you found this page helpful?

    


See existing feedback here.