Page History

Versions Compared

Old Version 4

changes.mady.by.user Unknown User (jofe)

Saved on Dec 11, 2020

compared with

New Version Current

changes.mady.by.user Andreia Costa

Saved on Jun 21, 2021

Key

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

...

You can also use the translated name of Overall Execution Status to get the same information.

Language	Translated Name
ES	Estado

del Grupo

Tests

ejecución general
DE	Allgemeiner Ausführungsstatus
FR	État d'Exécution Global

See the example:

Code Block

title	Expand to see the examples on sample code
collapse	true

Todo: ${Estado delde Grupoejecución de Testsgeneral.TODO}% (${Estado delde Grupoejecución de Testsgeneral.TODO.Count})
Fail: ${Estado delde Grupoejecución de Testsgeneral.FAIL}% (${Estado delde Grupoejecución de Testsgeneral.FAIL.Count})
Pass: ${Estado delde Grupoejecución de Testsgeneral.PASS}% (${Estado delde Grupoejecución de Testsgeneral.PASS.Count})
Executing: ${Estado delde Grupo deejecución Testsgeneral.EXECUTING}% (${Estado delde Grupoejecución de Testsgeneral.EXECUTING.Count})
Aborted: ${Estado delde Grupoejecución de Testsgeneral.ABORTED}% (${Estado delde Grupoejecución de Testsgeneral.ABORTED.Count})

Iterating Test Runs associated with a Test Execution

...

Document Generator allows rendering of the Pre-Conditions associated with a Test from a Test Run.

Definition:

${TestRuns[n].PreCondition.Field} -

Status

colour	Yellow
title	DEPRECATED

${TestRuns[n].PreConditions[p].Field}

n is the index of Test Runs, starting from 0. The fields available for Pre-Conditions are:

...

Code Block

title	Expand to see the example on sample code
collapse	true

#Iterating over Test Runs
#{for testruns}
	    #Getting data from Pre-Condition
	Pre-Condition Key:Conditions
    ${TestRuns[n].PreCondition.Key}
	PreConditionsCount}
    #{for p=TestRuns[n].PreConditionsCount}
      Pre-Condition SummaryKey: ${TestRuns[n].PreCondition.Summary}
	Condition:	PreConditions[p].Key}
      Pre-Condition Summary: ${TestRuns[n].PreCondition.Conditions}
	Type: PreConditions[p].Summary}
      Condition:  ${TestRuns[n].PreCondition.Pre-Condition Type}
#{end}

Iterating Attachments associated with a Test Run

Document Generator allows rendering of all the Attachments associated with a Test Run.

Definition:

PreConditions[p].Conditions}
      Type: ${TestRuns[n].

...

PreConditions[

...

p].Pre-Condition Type}
   #{end}
#{end}

Code Block

title	DEPRECATED - Expand to see the example

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

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

Example:

Code Block

title	Expand to see the example on sample code
collapse	true

#Iterating over Test Runs
#{for testruns}
	#Iterating#Getting data Testfrom AttachmentsPre-Condition
	#{for sa=TestRuns[n].AttachmentsCount}
		NamePre-Condition Key: ${TestRuns[n].Attachments[sa].NamePreCondition.Key}
		AuthorPre-Condition Summary: ${TestRuns[n].Attachments[sa].AuthorPreCondition.Summary}
	Condition:	ID: ${TestRuns[n].Attachments[sa].IDPreCondition.Conditions}
		SizeType: ${TestRuns[n].Attachments[sa].Size}
	#{endPreCondition.Pre-Condition Type}
#{end}

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

...

Iterating Attachments associated with a Test Run

Document Generator allows rendering of all the Evidences Attachments associated with a Test Run.

Definition:

$ {TestRuns[n].ExecutionEvidencesAttachmentsCount[dsa]}

d sa is the index of the EvidencesAttachments, starting from 0. The field ExecutionEvidencesCountAttachmentsCount was created in order to give the total number of Evidences Attachments of a Test Run.

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

...

Code Block

title	Expand to see the example on sample code
collapse	true

#Iterating over Test Runs
#{for testruns}
	#Iterating overTest EvidencesAttachments
	#{for dsa=TestRuns[n].ExecutionEvidencesCountAttachmentsCount}
		IdName: ${TestRuns[n].ExecutionEvidencesAttachments[dsa].IdName}
		NameAuthor: ${TestRuns[n].ExecutionEvidencesAttachments[dsa].NameAuthor}
		AuthorID: ${TestRuns[n].ExecutionEvidencesAttachments[dsa].AuthorID}
		LinkSize: @{title=${TestRuns[n].ExecutionEvidencesAttachments[dsa].FileURL}|href=Size}
	#{end}
#{end}

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

Iterating Evidences associated with a Test Run

Document Generator allows rendering of all the Evidences associated with a Test Run.

Definition:

$ {TestRuns[n].ExecutionEvidences[d]}

d is the index of the Evidences, starting from 0. The field ExecutionEvidencesCount was created in order to give the total number of Evidences of a Test Run.

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

Example:

Code Block

title	Expand to see the example on sample code
collapse	true

#Iterating over Test Runs
#{for testruns}
	#Iterating over Evidences
	#{for d=TestRuns[n].ExecutionEvidencesCount}
		Id.FileURL}}
		Size: ${TestRuns[n].ExecutionEvidences[d].Size}
		Created: ${TestRuns[n].ExecutionEvidences[d].Created}
		HumanReadableSize: ${TestRuns[n].ExecutionEvidences[d].HumanReadableSizeId}
		MimeTypeName: ${TestRuns[n].ExecutionEvidences[d].MimeTypeName}
		EvidenceAuthor: ${TestRuns[n].ExecutionEvidences[d].EvidenceAuthor}
		#{end}
#{end}

Iterating Defects associated with a Test Run

Document Generator allows rendering of all the defects associated with a Test Run.

Definition:

Link: @{title=${TestRuns[n].ExecutionEvidences[d].FileURL}|href=${TestRuns[n].ExecutionEvidences[d].FileURL}}
		Size: ${TestRuns[n].

...

ExecutionEvidences[

...

d]

...

e is the index of the defects, starting from 0. The field ExecutionDefectsCount was created in order to give the total number of Defects of a Test Run.

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

Example:

Code Block

title	Expand to see the example on sample code
collapse	true

#Iterating over Test Runs
#{for testruns}
	#Iterating over defects from each test run
	#{for e=TestRuns[n].ExecutionDefectsCount}
		Link: @{title=.Size}
		Created: ${TestRuns[n].ExecutionEvidences[d].Created}
		HumanReadableSize: ${TestRuns[n].ExecutionEvidences[d].HumanReadableSize}
		MimeType: ${TestRuns[n].ExecutionEvidences[d].MimeType}
		Evidence:${TestRuns[n].ExecutionDefectsExecutionEvidences[e].Key}|href=${BaseURL}/browse/${TestRuns[n].ExecutionDefects[e].Key}}
		Summary: ${TestRuns[n].ExecutionDefects[e].Summaryd].Evidence}
	#{end}
#{end}

Iterating

...

Defects associated with a Test Run

Document Generator allows rendering of all the Details from Automated Tests defects associated with a Test Run.

Definition:

Cucumber Scenario: $ {TestRuns[n].Cucumber Scenario}

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

ExecutionDefects[e]}

e is n is the index of the Test Runsdefects, starting from 0. The fields Cucumber Scenario/Generic Test Definition were field ExecutionDefectsCount was created in order to give the step details of Automated Tests total number of Defects of a Test Run.

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

...

Code Block

title	Expand to see the example on sample code
collapse	true

#Iterating over Test Runs
#{for testruns}
	#Test Run Step Details
	Cucumber Scenario: ${#Iterating over defects from each test run
	#{for e=TestRuns[n].Cucumber ScenarioExecutionDefectsCount}
	Test Definition	Link: $@{title=${TestRuns[n].Generic Test Definition].ExecutionDefects[e].Key}|href=${BaseURL}/browse/${TestRuns[n].ExecutionDefects[e].Key}}
		Summary: ${TestRuns[n].ExecutionDefects[e].Summary}
	#{end}
#{end}

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

Iterating Manual Test Step details associated with a Test Run

Iterating Automated Test details associated with a Test Run

Document Generator allows rendering of the Details from Manual Automated Tests associated with a Test Run.

Definition:

Cucumber Scenario: $ {TestRuns[n].TestSteps[r]}Cucumber Scenario}

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

n r is the index of the Test StepsRuns, starting from 0. The field TestStepsCount or TeststepsCount was fields Cucumber Scenario/Generic Test Definition were created in order to give the step details of Manual Automated Tests of a Test Run.

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

...

Code Block

title	Expand to see the example on sample code
collapse	true

#Iterating over Test Runs
#{for testruns}
	#Iterating#Test overRun Manual Test Steps from Test Run
	#{for r=TestRuns[n].TestStepsCount}
		StepNumber:	Step Details
	Cucumber Scenario: ${TestRuns[n].TestSteps[r].StepNumberCucumber Scenario}
		ActionTest Definition: ${wiki:TestRuns[n].TestSteps[r].Action}
		Data: ${wiki:TestRuns[n].TestSteps[r].Data}
		Expected Result: ${wiki:Generic Test Definition}
#{end}

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

Iterating Manual Test Step details associated with a Test Run

Document Generator allows rendering of the Details from Manual Tests associated with a Test Run.

Definition:

$ {TestRuns[n].TestSteps[r]}

r is the index of the Test Steps, starting from 0. The field TestStepsCount or TeststepsCount was created in order to give the step details of Manual Tests of a Test Run.

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

Example:

Code Block

title	Expand to see the example on sample code
collapse	true

#Iterating over Test Runs
#{for testruns}
	#Iterating over Manual Test Steps from Test Run
	#{for r=TestRuns[n].TestStepsCount}
		StepNumber:	${.ExpectedResult}
		Comment: ${wiki:TestRuns[n].TestSteps[r].Comment}
		Status:	${TestRuns[n].TestSteps[r].Status}
		Actual Result: ${wiki:TestRuns[n].TestSteps[r].Actual Result}StepNumber}
	#{end}
#{end}

Iterating Manual Test Step Attachments associated with a Test Run

Document Generator allows rendering of the Attachments from Manual Tests Steps associated with a Test Run.

Definition:

...

	Action: ${wiki:TestRuns[n].TestSteps[r].Action}
		Data: ${wiki:TestRuns[n].TestSteps[r].

...

sa is the index of the Test Step Attachments, starting from 0. The field AttachmentsCount was created in order to give the step attachments of Manual Tests of a Test Run.

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

Example:

Code Block

title	Expand to see the example on sample code
collapse	true

#Iterating over Test Runs
#{for testruns}
	#Iterating over Manual Test Steps from Test Run
	#{for r=TestRuns[n].TestStepsCount}
		#Iterating over Test Step Attachments
		#{for sa=TestRuns[n].TestSteps[r].AttachmentsCount}
			Name: {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].Attachments[sa].NameActual Result}
			Author: {TestRuns[n].TestSteps[r].Attachments[sa].Author}
			Link: {title=#{end}
#{end}

Iterating Manual Test Step Attachments associated with a Test Run

Document Generator allows rendering of the Attachments from Manual Tests Steps associated with a Test Run.

Definition:

$ {TestRuns[n].TestSteps[r].Attachments[sa]

...

}

sa is the index of the Test Step Attachments, starting from 0. The field AttachmentsCount was created in order to give the step attachments of Manual Tests of a Test Run.

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

Example:

Code Block

title	Expand to see the example

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

Iterating Manual Test Step Defects associated with a Test Run

Document Generator allows rendering of the Defects from Manual Tests Steps associated with a Test Run.

Definition:

...

$ {TestRuns[n].TestSteps[r].Defects[dc]}

dc is the index of the Test Step Defects, starting from 0. The field DefectsCount was created in order to give the step defects of Manual Tests of a Test Run.

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

Example:

Code Block

title	Expand to see the example on sample code
collapse	true

#Iterating over Test Runs
#{for testruns}
	#Iterating over Manual Test Steps from Test Run
	#{for r=TestRuns[n].TestStepsCount}
		#Iterating over Test Step DefectsAttachments
		#{for dcsa=TestRuns[n].TestSteps[r].DefectsCountAttachmentsCount}
			LinkName: {title={TestRuns[n].TestSteps[r].DefectsAttachments[dcsa].Key}|href={BaseURL}/browse/{Name}
			Author: {TestRuns[n].TestSteps[r].DefectsAttachments[dcsa].Key}Author}
			SummaryLink: {wiki:{title={TestRuns[n].TestSteps[r].Attachments[sa].FileURL}|href={TestRuns[n].TestSteps[r].DefectsAttachments[dcsa].SummaryFileURL}}
		#{end}

	#{end}
#{end}	Size: {TestRuns[n].TestSteps[r].Attachments[sa].Size}
		#{end}
	#{end}	
#{end}

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

Iterating Manual Test Step

...

Defects associated with a Test Run

Document Generator allows rendering of the Evidences Defects from Manual Tests Steps associated with a Test Run.

...

$ {TestRuns[n].TestSteps[r].EvidencesDefects[edc]}

e dc is the index of the Test Step EvidencesDefects, starting from 0. The field EvidencesCountDefectsCount was created in order to give the step evidences defects of Manual Tests of a Test Run.

...

Code Block

title	Expand to see the example on sample code
collapse	true

#Iterating over Test Runs
#{for testruns}
	#Iterating over Manual Test Steps from Test Run
	#{for r=TestRuns[n].TestStepsCount}
		#Iterating over Test Step EvidencesDefects
		#{for edc=TestRuns[n].TestSteps[r].EvidencesCountDefectsCount}
			NameLink: ${title={TestRuns[n].TestSteps[r].EvidencesDefects[edc].Name}
			Author: $Key}|href={BaseURL}/browse/{TestRuns[n].TestSteps[r].EvidencesDefects[edc].AuthorKey}}
			LinkSummary: @{title=${{wiki:TestRuns[n].TestSteps[r].EvidencesDefects[edc].FileURL}|href=${TestRuns[n].TestSteps[r].Evidences[e].FileURL}}
			Size: ${TestRuns[n].TestSteps[r].Evidences[e].Size}
        	Created: Summary}
		#{end}

	#{end}
#{end}

Iterating Manual Test Step Evidences associated with a Test Run

Document Generator allows rendering of the Evidences from Manual Tests Steps associated with a Test Run.

Definition:

$ {TestRuns[n].TestSteps[r].Evidences[e]}

e is the index of the Test Step Evidences, starting from 0. The field EvidencesCount was created in order to give the step evidences of Manual Tests of a Test Run.

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

Example:

Code Block

title	Expand to see the example on sample code
collapse	true

#Iterating over Test Runs
#{for testruns}
	#Iterating over Manual Test Steps from Test Run
	#{for r=TestRuns[n].TestStepsCount}
		#Iterating over Test Step Evidences
		#{for e=TestRuns[n].TestSteps[r].EvidencesCount}
			Name: .Created}
        	HumanReadableSize: ${TestRuns[n].TestSteps[r].Evidences[e].HumanReadableSize}
        	MimeType: ${TestRuns[n].TestSteps[r].Evidences[e].MimeType}
        	Evidence:${TestRuns[n].TestSteps[r].Evidences[e].EvidenceName}
			#{end}

	#{end}
#{end}

Info

If you want to export the images, for example

Author: ${TestRuns[n].TestSteps[r].Evidences[e].Author}
			Link: @{title=${TestRuns[n].TestSteps[r].Evidences[e].FileURL}|href=${TestRuns[n].TestSteps[r].

ExecutionEvidences

Evidences[

e].FileURL}

you can check here for instructions on how to do it.

Manual Test Step Custom Fields associated with a Test Run

To export Test Steps Custom Fields within a Test Run you just have to define the placeholder with the name of your custom field.

Example: Image that you have a custom field called "Run CF". To get the value printed on your document you just have to use the following placeholder:

Code Block

#Iterating over Test Runs
#{for testruns}
	#Iterating over Manual Test Steps from Test Run
	#{for r=TestRuns[n].TestStepsCount}
		#Add Custom Field name, for example Run CF
		Run CF: ${TestRuns[n].TestSteps[r].Run CF}
	#{end}
#{end}

Info
If your custom field type is a Number, Data, or Date Time you can use formatting functions.

Exporting Test Run Activity

Document Generator allows export all the activity of a Test Run.

Definition:

...

$ {TestRuns[n].ActivityEntries[ac]}

}
			Size: ${TestRuns[n].TestSteps[r].Evidences[e].Size}
        	Created: ${TestRuns[n].TestSteps[r].Evidences[e].Created}
        	HumanReadableSize: ${TestRuns[n].TestSteps[r].Evidences[e].HumanReadableSize}
        	MimeType: ${TestRuns[n].TestSteps[r].Evidences[e].MimeType}
        	Evidence:${TestRuns[n].TestSteps[r].Evidences[e].Evidence}
			#{end}

	#{end}
#{end}

Info
If you want to export the images, for example ${TestRuns[n].ExecutionEvidences[d].FileURL} you can check here for instructions on how to do it.

Manual Test Step Custom Fields associated with a Test Run

To export Test Steps Custom Fields within a Test Run you just have to define the placeholder with the name of your custom field.

Example: Image that you have a custom field called "Run CF". To get the value printed on your document you just have to use the following placeholder:

Code Block

#Iterating over Test Runs
#{for testruns}
	#Iterating over Manual Test Steps from Test Run
	#{for r=TestRuns[n].TestStepsCount}
		#Add Custom Field name, for example Run CF
		Run CF: ${TestRuns[n].TestSteps[r].Run CF}
	#{end}
#{end}

Info
If your custom field type is a Number, Data, or Date Time you can use formatting functions.

Exporting Test Run Activity

Document Generator allows export all the activity of a Test Run.

Definition:

$ {TestRuns[n].ActivityEntries[ac]}

ac is the index of the Activity entry, starting from 0. The field ActivityEntriesCount was created in order to give the Activity entry of a Test Run.

Example:

Code Block

title	Expand to see the example on sample code
collapse	true

#{for testruns}
#{for d=TestRuns[n].ActivityEntriesCount}
Action: ${TestRuns[n].ActivityEntries[d].Action}
Author: ${TestRuns[n].ActivityEntries[d].Author}
Created at: ${dateformat("dd-MM-yyyy HH:mm:ss"):TestRuns[n].ActivityEntries[d].Created}
Changes:
#{for ch=TestRuns[n].ActivityEntries[d].ActivityItemsCount}
Field: ${TestRuns[n].ActivityEntries[d].ActivityItems[ch].Field}
OldValue: ${TestRuns[n].ActivityEntries[d].ChangedItems[ch].OldValue}
NewValue: ${TestRuns[n].ActivityEntries[d].ChangedItems[ch].NewValue}

#{end}
#{end}
#{end}

Exporting Parameterized Tests from a Test Run

To export all this data, we first need to execute the test run. If we change any data, we need to return to the Execution Page and merge it with the new data.

Fields	Description
IsDataDriven	Returns "true" if the current test run is data-driven; otherwise, it returns "false"
Iterations Overall Execution Status.STATUS.Percentage	The percentage of STATUS in the test run iterations
IterationsOverallExecutionStatus	List of all the statuses in the current test run iteration and their percentages
IterationsOverallExecutionStatus.STATUS.Count	The number of STATUS in the test run iterations
Parameters	List of the parameters from each test run iteration
ParametersCount	Total of Parameters declared in Dataset

Info

title	Data-driven

The field IsDataDriven is going to return TRUE only if the test run has more than one iteration.

Exporting Test Runs Parameters from a Test Execution

For each Test Run Parameter you can export the following fields:

Key
Value

Below you can find an example of how to iterate over the list of Test Run Parameters associated with a Test Execution.

Code Block

title	Some mappings we can export from Test Runs Parameters

// Iterating each test run
#{for testruns}
    // Iterating over parameters for each test run
    Parameters Total: ${TestRuns[n].ParametersCount}
    #{for m=TestRuns[n].ParametersCount}
        Key: ${TestRuns[n].Parameters[m].Key}
        Value: ${TestRuns[n].Parameters[m].Value}
    #{end}
#{end}

Exporting Test Runs Iterations from a Test Execution

For each Test Run Iteration you can export the following fields:

Overall Execution Status
Data from Test Run Iterations
Parameters from Test Run Iterations
PreConditions from Test Run Iterations
Test steps from Test Run Iterations

Below you can find an example of how to iterate over the list of Test Run Iterations associated with a Test Execution.

Code Block

title	Some mappings we can export from Test Run Iterations

// Iterating each test run
#{for testruns}
    IsDataDriven: ${TestRuns[n].IsDataDriven}  
     
    // Iterations Overall Execution Status (percentage + total of testes per status)
    List of Statuses: ${TestRuns[n].Iterations Overall Execution Status}
    TO DO: ${TestRuns[n].Iterations Overall Execution Status.TO DO}% - ${TestRuns[n].Iterations Overall Execution Status.TO DO.Count}
    EXECUTING: ${TestRuns[n].Iterations Overall Execution Status.EXECUTING}% - ${TestRuns[n].Iterations Overall Execution Status.EXECUTING.Count}
    PASSED: ${TestRuns[n].Iterations Overall Execution Status.PASSED}% - ${TestRuns[n].Iterations Overall Execution Status.PASSED.Count}
    FAILED: ${TestRuns[n].Iterations Overall Execution Status.FAILED}% - ${TestRuns[n].Iterations Overall Execution Status.FAILED.Count}
    ABORTED: ${TestRuns[n].Iterations Overall Execution Status.ABORTED}% - ${TestRuns[n].Iterations Overall Execution Status.ABORTED.Count}
 
    // Iterating over test runs iterations
    Total of Iterations from a Test Run: ${TestRuns[n].IterationsCount}
    #{for m=TestRuns[n].IterationsCount}
        Name: ${TestRuns[n].Iterations[m].Name}
        Status: ${TestRuns[n].Iterations[m].Status}
        Parameters: ${TestRuns[n].Iterations[m].Parameters}
 
        // Iterating over parameters for each test run iteration
        Parameters Total: ${TestRuns[n].Iterations[m].ParametersCount}
        #{for l=TestRuns[n].Iterations[m].ParametersCount}
            Key: ${TestRuns[n].Iterations[m].Parameters[l].Key}
            Value: ${TestRuns[n].Iterations[m].Parameters[l].Value}
        #{end}
 
        // Iterating over preconditions for each test run iteration
        Preconditions Total: ${TestRuns[n].Iterations[m].PreConditionsCount}
        #{for l=TestRuns[n].Iterations[m].PreConditionsCount}
			Key: ${TestRuns[n].Iterations[m].PreConditions[l].Key}
			Summary: ${TestRuns[n].Iterations[m].PreConditions[l].Summary}
            Definition: ${TestRuns[n].Iterations[m].PreConditions[l].Conditions}
            Type: ${TestRuns[n].Iterations[m].PreConditions[l].Pre-Condition Type}
        #{end}
 
        //Iterating over test steps for each test run iteration
        #{for i=TestRuns[n].Iterations[m].TestStepsCount}
            Step Number: ${TestRuns[n].Iterations[m].TestSteps[i].StepNumber}
            Action: ${TestRuns[n].Iterations[m].TestSteps[i].Action}
            Data: ${TestRuns[n].Iterations[m].TestSteps[i].Data}
            Expected Result: ${TestRuns[n].Iterations[m].TestSteps[i].ExpectedResult}
            Status: ${TestRuns[n].Iterations[m].TestSteps[i].Status}
            Comment: ${TestRuns[n].Iterations[m].TestSteps[i].Comment}
            Actual Result: ${TestRuns[n].Iterations[m].TestSteps[i].ActualResult}
            // Replace the placeholder text to export any custom field associated with the test step.
            Step Custom Field:${TestRuns[n].Iterations[m].TestSteps[i].<Step Custom Field>}
             
            // Iteration Test Step Attachments
            #{for l=TestRuns[n].Iterations[m].TestSteps[i].AttachmentsCount}
                Id: ${TestRuns[n].Iterations[m].TestSteps[i].Attachments[l].Id}
                Name: ${TestRuns[n].Iterations[m].TestSteps[i].Attachments[l].Name}
                Image: ${TestRuns[n].Iterations[m].TestSteps[i].Attachments[l].Attachment}
                FileURL: ${TestRuns[n].Iterations[m].TestSteps[i].Attachments[l].FileURL}
            #{end}
            // Iteration Test Step Evidences
            #{for l=TestRuns[n].Iterations[m].TestSteps[i].EvidencesCount}
                Id: ${TestRuns[n].Iterations[m].TestSteps[i].Evidences[l].Id}
                Name: ${TestRuns[n].Iterations[m].TestSteps[i].Evidences[l].Name}
                Evidence

ac is the index of the Activity entry, starting from 0. The field ActivityEntriesCount was created in order to give the Activity entry of a Test Run.

Example:

Code Block

title	Expand to see the example on sample code
collapse	true

#{for testruns}
#{for d=TestRuns[n].ActivityEntriesCount}
Action: ${TestRuns[n].ActivityEntriesIterations[dm].Action}
Author: ${TestRuns[nTestSteps[i].ActivityEntriesEvidences[d].Author}
Created at: ${dateformat("dd-MM-yyyy HH:mm:ss"):TestRuns[n].ActivityEntries[d].Created}
Changes:
#{for ch=TestRuns[n].ActivityEntries[d].ActivityItemsCount}
Fieldl].Evidence}
            #{end}
            // Iteration Test Step Defects
            #{for l=TestRuns[n].Iterations[m].TestSteps[i].DefectsCount}
                Description: ${TestRuns[n].Iterations[m].TestSteps[i].Defects[l].Description}
                Id: ${TestRuns[n].Iterations[m].ActivityEntriesTestSteps[di].ActivityItemsDefects[chl].FieldId}
OldValue                Key: ${TestRuns[nn].Iterations[m].ActivityEntriesTestSteps[di].ChangedItemsDefects[chl].OldValueKey}
NewValue                Summary: ${TestRuns[n].ActivityEntries[dIterations[m].TestSteps[i].ChangedItemsDefects[chl].NewValueSummary}
            #{end}
        #{end}
    #{end}
#{end}

Content

Space Tools

Versions Compared

Old Version 4

New Version Current

Key

Iterating Test Runs associated with a Test Execution

Iterating Attachments associated with a Test Run

Iterating Attachments associated with a Test Run

Iterating Evidences associated with a Test Run

Iterating Defects associated with a Test Run

Iterating

Defects associated with a Test Run

Iterating Manual Test Step details associated with a Test Run

Iterating Automated Test details associated with a Test Run

Iterating Manual Test Step details associated with a Test Run

Iterating Manual Test Step Attachments associated with a Test Run

Iterating Manual Test Step Attachments associated with a Test Run

Iterating Manual Test Step Defects associated with a Test Run

Iterating Manual Test Step

Defects associated with a Test Run

Iterating Manual Test Step Evidences associated with a Test Run

Manual Test Step Custom Fields associated with a Test Run

Exporting Test Run Activity

Manual Test Step Custom Fields associated with a Test Run

Exporting Test Run Activity

Exporting Parameterized Tests from a Test Run