The Execution Dashboard is where test runs are tracked in real time. It opens automatically when you click Execute Plan from the Test Plans screen, and can also be navigated to directly via the TestGenie sidebar.
Starting a Test Run
A test run begins when you click Execute Plan from a Test Plan's detail view.
TestGenie:
Creates a Test Execution issue in Jira (using the issue type configured in Issue Mapping → Execution Planning)
Links the execution to the Test Plan and to each Test Case in the plan
Opens the Execution Dashboard showing all test cases in the run, all with status Not Executed
Each click of Execute Plan creates a separate, independent run. Previous runs are preserved and accessible via the Active Runs sidebar.
The left sidebar lists all execution runs for the current plan.
Each run is shown with its name or number
Click a run to load it in the main panel
Multiple runs for the same plan allow you to track results across different dates, environments, or testers
Stat Cards
Three stat cards appear at the top of the Execution Dashboard and update live as you mark results:
Card | What it shows |
|---|
Tests Passed | Number of test cases marked as Passed in this run |
Tests Failed | Number of test cases marked as Failed in this run |
Not Executed | Number of test cases with no result recorded yet |
The total of all three cards always equals the number of test cases in the run.
Test Case Table
The main table shows every test case in the active run. Columns include:
Column | Description |
|---|
P | Priority indicator |
Key | The Jira issue key of the test case — click to open the full issue |
Summary | The test case title |
Assignee | The team member assigned to this test case |
TEST RESULT | Dropdown for marking the result |
ACTIONS | Available actions for this test case (defect link action appears when Failed is selected) |
Marking Test Results
In the TEST RESULT column, select one of three outcomes for each test case:
Result | When to use |
|---|
Passed | The test case executed successfully and the expected result was achieved |
Failed | The test case executed but the expected result was not achieved — a defect was found |
Not Executed | The test case was not run in this session (default state) |
Results are saved immediately when selected. The stat cards update automatically.
Linking Defects to Failed Tests
When a test case is marked Failed, the ACTIONS column shows a defect link option.
To link a defect:
Mark the test result as Failed.
In the ACTIONS column, click the defect link action.
Search for and select the existing Jira defect to link.
Confirm — two links are created automatically:
Prerequisite: The Defect Orchestration section in Issue Mapping must be fully configured for the defect link action to appear.
Export Report
Click Export Report (top-right toolbar) to generate a downloadable report of the current run.
See the Export Report page for details on what is included and how to share it.
Filtering in the Execution Dashboard
Use the filter controls to narrow the test case table:
By Assignee — show only test cases assigned to a specific team member
By Status / Result — show only Passed, Failed, or Not Executed test cases
By Sprint — filter by Jira sprint association
Filter preferences are preserved across sessions.
Multiple Runs per Plan
Running the same plan multiple times is common — for example:
One run per sprint against the same regression suite
One run for staging and one run for production
A re-run after defects from the first run are fixed
Each run is independent. Results from run 1 are not overwritten by run 2. Use the Active Runs sidebar to compare results across runs.