Versions Compared

Version Old Version 1 New Version 2
Changes made by

APPWRK Writer

Noopur Varshney [AIO Tests]

Saved on

Key

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

Execution Distribution report allows managers to view cycle execution progress by different parameters. By using the information in this report, managers can prioritize work to meet their testing goals. This report is generated for the specified cycle(s) and gives distribution by users assigned to cases for execution, case priority, case type, tags added to cases and by user requirements (Jira issues linked to cases). You can also use any of the case and cycle level custom fields to group data by.

...

  1. Cycle Summary: The first section of the Multi Cycle Execution Distribution report consists of the Key, Title, Objective,  Start Start date and End date.

  2. Case Distribution: In the Case distribution section, the bar chart shows the case count by the selected distribution parameter broken down by the last run status of cases.

  3. Estimated Effort Distribution: In the estimated effort distribution, the bar chart shows the Remaining and Completed Est. Effort for cases that fall under the selected distribution parameter. Completed estimated effort is the total of estimated effort for completed cases (cases in Passed/Failed status). Similarly, the remaining estimated effort is the total of the estimated effort for incomplete cases (cases in Blocked/In Progress/Not Run status).

  4. Execution Data: In this section, the data represented in bar charts is shown in the table format- case count by selected distribution parameter and by last run status, estimated, actual and remaining effort and number of incomplete cases. 

Info

  • In the execution data section, there is an "Only show rows with pending executions" checkbox. If checked, the table shows the distribution for cases that have not yet been executed.

  • There are a few important points that should be noted.

    • Each case is mapped uniquely (except for tags and requirements distribution parameters).

    • Estimated Effort is the effort entered by the user while creating the case.

    • Actual Effort is the total effort logged across all runs.

    • A case is considered complete if the status is either Passed or Failed.

    • A case is considered incomplete if the status is either Not Run, In Progress or Blocked.

    • When all assigned work is completed or if no estimated effort has been entered on the case, then Remaining Effort = 0.

...

Distribution by User Assignment

...