Dashboard Widgets
Last updated
Avo Assure - User Guide v23.1
Last updated
This widget visualises the execution summary based on complete and incomplete executions.
Complete– Total number of executions that have been assigned and completed. (Includes both “Pass” and “Fail” scenarios)
Incomplete– Total number of executions that are assigned but not executed.
This widget displays the number of remaining available days for task completion based on the latest end date given, out of all the assigned test suites. (Task end date)
This widget visualizes the execution summary based on complete and pending executions.
Pending– Total number of tasks (MODULES/SCENARIOS/TESTCASES) that are assigned but not yet completed.
Complete– Total number of tasks (MODULES/SCENARIOS/TESTCASES) that have been submitted and approved.
This widget displays the execution status for test suites. Overall test scenario statuses include: Fail, Terminate, Pass, Incomplete, and Skipped.
This widget displays the execution analysis based on module names, their scenarios, respective overall execution status, and the report count for these test suites.
This widget visualizes the test cases based on their current state.
This widget visualises the total count of executions initiated by the respective assignees.
Note: Migrated data will have admin as default.
This widget visualises the executions done per day based on their status.
Note: Only “Pass” and “Fail” execution statuses will be displayed via this widget.
This widget visualises the count based on the status (Pass/Fail/Terminated) of executed scenarios.
Pass – Total number of scenario executions that have passed.
Fail – Total number of scenario executions that have failed.
Terminate – Total number of scenario executions that have failed.
Note: To visualise these counts for any given scenario, choose the ‘Testscenarios.name’ or ‘Testscenarios.testscenarioid’ as the widget’s filter.
This widget displays the number of unique scenarios executed over a period of time.
This widget displays the number of unique existing steps (ignores test steps in reused test cases). To visualise these counts for detailed insights, choose any of the following filters for this widget.
Projects.name: To get the number of unique test steps within a project based on the project name.
Projects.projectid: To get the number of unique test steps within a project based on the project ID.
Testsuites.name: To get the number of unique test steps within a module based on the module name.
Testsuites.testsuiteid: To get the number of unique test steps within a module based on the module ID.
Testscenarios.name: To get the number of unique test steps within a scenario based on the scenario name.
Testscenarios.testscenarioid: To get the number of unique test steps within a scenario based on the scenario ID.
This widget visualizes the defects logged over a period of time.
The header within the widget displays the summarized number of the issues based on the priorities.
The main chart is plotted with the number of issue counts over the Y-axis and the dates over the X-axis. These counts are stacked up based on the priorities (Major/ Minor/ High/ Highest/ Low/ Medium/ Lowest) and can be easily differentiated based on their colors.
This widget visualizes the defects trend (Recording the defects’ state from “Open” to “Closed”) represented by a line chart over a period of time. This line chart is plotted with the number of issue counts over the Y-axis and the date over the X-axis.
This widget visualizes the defects trend for defects having states as either “Open” or “Resolved” represented by a bar chart over a period of time. This chart is plotted with the number of issue counts over the Y-axis and the date over the X-axis.
The total defects that created (Open) and resolved are summarized at the widgets' top section.
Jira sprint health is recorded based on the status of the issues that are part of the sprint. This widget visualizes the Jira sprint health based on the total count of the sprint issues and their states.
Jira sprint burn-down is recorded over the period of the sprint start date till the sprint end date.
This widget visualizes the Sprint burn-down by depicting the amount of work pending over the Y-axis and the time spent (days) over the X-axis.
Note: Two lines are plotted in the Jira Sprint Burn-Down widget. One displaying the ideal progress in sprint burn-down and the other depicting the current progress.
This widget visualizes the data which illustrates the defects logged into Jira via Avo Assure. It displays the defects based on their current status in Jira. It also displays the user name of the user, who initiated the execution in Avo Assure.
The chart displays the execution count along the X-axis and the “executed by” user name along the Y-axis.
This widget visualizes the summary of the defects based on their statuses that are logged in Jira via Avo Assure.
