Uploaded image for project: 'Xray for Jira'
  1. Xray for Jira
  2. XRAY-7627

As system, whenever importing Behave JSON results using the REST API, it should be possible to define some Test Execution related parameters

    XporterXMLWordPrintable

Details

    • Suggestion
    • Status: New
    • Resolution: Unresolved
    • None
    • None
    • REST_API
    • None
    • UNCOVERED

    Description

      As a system, whenever importing Behave JSON results using the REST API, it should be possible to define some Test Execution related parameters.

       

      The current Behave JSON endpoint (the standard one) should be evolved to support some parameters identified in the URL.

       

       POST /rest/raven/1.0/import/execution/behave
      

       

      PATH PARAMETERS
      parameter type description
      projectKey String
      • key of the project where the test execution (if the testExecKey parameter wasn't provided).
      testExecKey String - key of the Test Execution. This will override any reference to Test Execution that may come on the cucumber json report as a tag.
      testPlanKey String - key of the Test Plan; if you specify the Test Plan, the Tests will be added automatically to the Test Plan if they're not part of it.
      testEnvironments String - a string containing a list of test environments separated by ";"
      revision String - source code and documentation version used in the test execution.
      fixVersion String - the Fix Version associated with the test execution (it supports only one value).

      Attachments

        Issue Links

          Activity

            People

              helder.ferreira Helder Ferreira
              amgt Ana Teixeira
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated: