Versions Compared

Key

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


Note
titleTo open this report your current project must satisfy the following conditon

Test Execution or Sub Test Execution issue types are required in the issue type scheme.

Shows a list of Test Runs with detailed info for each one, including related Test, Test Execution and Test Plan entities, execution dates, linked defects among other.

...


Understanding the report columns

MetricNotes
TestKey of the Test associated with the TestRun.
Test SummarySummary of the Test associated with the Test Run.
ComponentsComponents of the Test associated with the Test Run.
Test PriorityPriority of the Test associated with the Test Run.
Test ExecutionKey of the Test Execution associated with the Test Run.
Test EnvironmentsTest Environments in which the Test has been executed. This corresponds to the respective Test Execution field.
Test PlanIf the Test Execution has been created in the context of a Test Plan, this column will display the Test Plan key.
Test TypeType of the Test Associated with the Test Run.
TestRun StatusThe status (i.e. result) of the TestRun.
Executed ByUser who has performed the execution.
Fix VersionFix Version associated to the Test Run. This corresponds to the respective Test Execution field.
RevisionRevision of the Test Execution associated with the Test Run.
Started AtDate of the TestRun start.
Finished AtDate of the TestRun end.
Elapsed TimeElapsed Time since the Begin of the TestRun. If the Status is not a final Status, then the elapsed time will be count as the time between the start date and the current time.
inked Defects

Defects directly associated with the related Test Runs. Will count as unique Defects (if the same Defect issue is added multiple times in the same Test Run it will count as one).

Defects having Resolution will be counted in the Closed column, every others will be counted in the Open column.

Example

Exporting the Report

...