The Execution Dashboard gives a live view of test execution results across all active runs for a project. It is the single screen that answers "what is the test status?" before any sprint review or release.
This page covers what the Execution Dashboard shows and how to use it. For step-by-step instructions on marking results, linking defects, and exporting, see the Test Execution page.
Accessing the Execution Dashboard
The Execution Dashboard opens automatically when you click Execute Plan in the Test Plans screen.
You can also navigate to it directly from the TestGenie sidebar — it will show the most recently active execution run.
Layout Overview
The Execution Dashboard has three main areas:
Area | Location | Purpose |
|---|
Active Runs sidebar | Left panel | Lists all execution runs for the current plan; click to switch between them |
Stat cards | Top of main panel | Live counts of Tests Passed, Tests Failed, and Not Executed |
Test case table | Main panel | Every test case in the active run with its result and actions |
Stat Cards
The three stat cards update in real time as results are marked:
Tests Passed — count of test cases marked Passed
Tests Failed — count of test cases marked Failed
Not Executed — count of test cases with no result yet
These cards are the fastest way to answer "what's the status?" during a run. At the start of any run, all counts are Not Executed. By release, the target is zero Not Executed.
Each time Execute Plan is clicked, a new run is created and added to the Active Runs sidebar.
Use the sidebar to:
Switch between runs for the same plan (e.g., run 1 and run 2 after a fix cycle)
Compare pass/fail counts across runs
Track re-test outcomes after defects are resolved
Runs are labelled by their creation date or execution issue key. All runs persist — no run overwrites another.
Test Case Table
The table lists every test case in the selected run. Key columns:
Column | Description |
|---|
P | Priority indicator for the test case |
Key | Jira issue key — click to open the test case in Jira |
Summary | Test case title |
Assignee | Team member responsible for this test case |
TEST RESULT | Dropdown — mark Passed, Failed, or Not Executed |
ACTIONS | Defect link action (visible when result is Failed) |
Results saved in the TEST RESULT column are stored immediately and reflected in the stat cards.
Filtering
Filter the test case table to focus on specific subsets:
By Assignee — show only test cases assigned to a specific person
By Result — show only Passed, Failed, or Not Executed rows
By Sprint — filter by Jira sprint
Filter preferences are remembered across sessions so you do not need to re-apply them each time.
The Export Report button (top-right toolbar) generates a report of the current run. See the Export Report page for details.
The Create Run button (top-right toolbar) starts a new execution run for the current plan without navigating back to the Test Plans screen. This is a shortcut for teams that run the same plan repeatedly.
How Results Are Stored
Execution results are stored in a lightweight SQL table managed by TestGenie inside the Atlassian Forge runtime. This is separate from the Jira issue properties but linked to the Execution issue by ID.
Results are project-scoped and tied to the specific execution run. They do not affect the Jira issue status of the test case — the Jira status and the execution result are independent.