Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Warning

If a Test Execution contains a lot of information, it can decrease Jira performance

Overall Execution Status

Export the Overall Execution Status with name and percentage for each Test Execution Status

Code Block
${Overall Execution Status}

You can print the status of the Test Execution by using the following notation:

% per StatusNumber of Tests per Status
${Overall Execution Status.NameOfStatus.Percentage}${Overall Execution Status.NameOfStatus.Count}

...

Code Block
titleExpand to see the examples on sample code of a Test Execution details
collapsetrue
Todo: ${Overall Execution Status.TODO.Percentage}% (${Overall Execution Status.TODO.Count})
Fail: ${Overall Execution Status.FAIL.Percentage}% (${Overall Execution Status.FAIL.Count})
Pass: ${Overall Execution Status.PASS.Percentage}% (${Overall Execution Status.PASS.Count})
Executing: ${Overall Execution Status.EXECUTING.Percentage}% (${Overall Execution Status.EXECUTING.Count})
Aborted: ${Overall Execution Status.ABORTED.Percentage}% (${Overall Execution Status.ABORTED.Count})

...

Code Block
titleExpand to see the example on sample code
collapsetrue
#Iterating over Test Runs
#{for testruns}
	#Iterating over defects from each test run
	#{for e=TestRuns[n].ExecutionDefectsCount}
		Link: @{title=${TestRuns[n].ExecutionDefects[e].Key}|href=${BaseURL}/browse/${TestRuns[n].ExecutionDefects[e].Key}}
		Summary: ${TestRuns[n].ExecutionDefects[e].Summary}
	#{end}
#{end}


Iterating Automated Test

...

details associated with a Test Run

Xporter for Jira allows rendering of all the Test Steps Attachments the Details from Automated Tests associated with a Test Run. 

Definition:

Cucumber Scenario: $ {TestRuns[n].

TestStepsAttachments[a]}

a is the index of the Test Steps Attachments, starting from 0. The field TestStepsAttachmentsCount was created in order to give the total of Test Steps Attachments of a Test Run.

Since a Test Run isn't a Jira Issue, you can render only the following mappings.

Example:

Code Block
titleExpand to see the example on sample code
collapsetrue
#Iterating over Test Runs
#{for testruns}
	#Iterating over TestSteps Attachments
	#{for a=TestRuns[n].TestStepsAttachmentsCount}
		Name: ${TestRuns[n].TestStepsAttachments[a].Name}
		Author: ${TestRuns[n].TestStepsAttachments[a].Author}
		Link: @{title=${TestRuns[n].TestStepsAttachments[a].FileURL}|href=${TestRuns[n].TestStepsAttachments[a].FileURL}}
		Size: ${TestRuns[n].TestStepsAttachments[a].Size}
	#{end}
#{end}
Warning

If a Test Execution contains lots of information it can decrease Jira performance

Iterating Automated Test details associated with a Test Run

Xporter for Jira allows rendering of the Details from Automated Tests associated with a Test Run. 

Definition:

Cucumber Scenario}

Test Definition: Cucumber Scenario: $ {TestRuns[n].Cucumber Scenario}Test Definition: $ {TestRuns[n].Generic Test Definition}

n is the index of the Test Runs, starting from 0. The fields Cucumber Scenario/Generic Test Definition were created in order to give the step details of Automated Tests of a Test Run.

...

Code Block
titleExpand to see the example on sample code
collapsetrue
#Iterating over Test Runs
#{for testruns}
	#Iterating over Manual Test Steps from Test Run
	#{for r=TestRuns[n].TestStepsCount}
		StepNumber:	${TestRuns[n].TestSteps[r].StepNumber}
		StepAction: ${wiki:TestRuns[n].TestSteps[r].StepAction}
		Data: ${wiki:TestRuns[n].TestSteps[r].Data}
		Expected Result: ${wiki:TestRuns[n].TestSteps[r].ExpectedResult}
		Comment: ${wiki:TestRuns[n].TestSteps[r].Comment}
		Status:	${TestRuns[n].TestSteps[r].Status}
		Actual Result: ${wiki:TestRuns[n].TestSteps[r].Actual Result}
	#{end}
#{end}

...