Page History

...

#Iterating over Test Runs
#{for testruns}
    Execution Status: ${TestRuns[n].Execution Status}
    AssigneeID: ${AssigneeId}
	Rank: ${TestRuns[n].Rank}
    Executed By: ${TestRuns[n].Executed By}
    Started On: ${TestRuns[n].Started On}
    Finished On: ${TestRuns[n].Finished On}
    Comment: ${wiki:TestRuns[n].Comment}
    Execution Defects Count: ${TestRuns[n].ExecutionDefectsCount}
    TestSteps Defects Count: ${TestRuns[n].TestStepsDefectsCount}
    Evidences Count: ${TestRuns[n].ExecutionEvidencesCount}
#{end}

Test Execution from a Test Run associated with Test

It is possible to access Test Execution information by iterating over tests and their Test Runs. The notation is: 

#{for tests}
	${Tests[n].Key}
	#{for c=Tests[n].TestRunsCount}
		${Tests[n].TestRuns[c].Executed By}
		${Tests[n].TestRuns[c].PreCondition.Key}

		${Tests[n].TestRuns[c].TestExecution.Key}
		${Tests[n].TestRuns[c].TestExecution.Summary}
		${Tests[n].TestRuns[c].TestExecution.Description}
		.......
	#{end}
#{end}

Exporting Test Runs custom fields

To export Test Runs Custom Fields you just have to defined define the placeholder with the name of you your custom field.

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

...

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.

...