Content:
Definition
Test Plan defines the objectives, resources, and processes for a specific test. Additionally, it is a bucket of suites or scenarios. Contain also information about reported bugs.
Available Panels
QA Craft Reports
General Metrics
Test Plan content and overall metrics
A main metric table. It shows the overall progress of the actions of the test. In the columns, there are:
| Column | Description |
|---|---|
| TS | Test Suite key. You can go to that TS page by clicking on it. |
| TS Name | Test Suite summary |
| TS Priority | Test Suite priority |
| TS Progress | Current Test Suite progress. It shows graphically various Test Case statuses connected to that Test Suite. |
| TC Passed | The number of passed Test Cases. You can list them by clicking on them. |
| TC Failed | The number of failed Test Cases. You can list them by clicking on them. |
| TC Blocked | The number of blocked Test Cases. You can list them by clicking on them. |
| TC Skipped | The number of skipped Test Cases. You can list them by clicking on them. |
TC None | The number of Test Cases without resolution, You can list them by clicking on them. |
| TC Total | The number of all Test Cases connected to the Test Suite. You can list them by clicking on them. |
| BUG Open | The number of unique unresolved Bugs reported to connected Test Cases. In the brackets, there is the number of Bugs related to Test Cases, including repetitions. You can list them by clicking on them. |
| BUG Total | The number of unique Bugs reported to connected Test Cases. In the brackets, there is the number of Bugs related to Test Cases, including repetitions. You can list them by clicking on them. |
| REQ Total | The number of connected requirements. |
All values could be sorted or filtered by choosing the right option from the column caption. In the last row, you can find a summary, counting all objects per column. When you select some rows, there will be presented a summary of selected Test Suites.
The grid content could be downloaded as a .csv file.
Test Case Metrics
Test Cases execution - grouped by day (idle days excluded)
The table contains information about executed Test Cases. It daily summarizes the number of Test Cases split between their resolutions.
| Column | Description |
|---|---|
| Date | Date when the Test Cases was executed. |
| Total TC | The number of all executed Test Cases. You can list them by clicking on them. |
| Passed | The number of passed Test Cases. You can list them by clicking on them. |
| Failed | The number of failed Test Cases. You can list them by clicking on them. |
| Blocked | The number of blocked Test Cases. You can list them by clicking on them. |
| Skipped | The number of skipped Test Cases. You can list them by clicking on them. |
Additionally, there is a checkbox Show only current iterations. Thanks to that, you can include or ignore previous Test Cases iterations.
The grid content could be downloaded as a .csv file.
Test Cases history
The table presents the whole history of Test Case execution.
| Column | Description |
|---|---|
| Execution Date | Date when the Test Cases was executed. |
| Test Case | Test Case key. You can go to that TC page by clicking on it. |
| Summary | Test Case summary |
| Iteration | The current Test Case iteration |
| Version | Software version |
| Environment | Test environment |
| Status | Test Case resolution |
| Requirement | The requirement, which is connected to Test Case. You can go to that page by clicking on it. |
Some rows are grayed out. They contain the previous iteration of the Test Case.
Additionally, there are some available actions:
| Action | Description |
|---|---|
| Show current iterations | Hides previous Test Case iterations when they are visible |
| Show all iterations | Shows all Test Case iteration when they are hidden |
| Group by Test Case | Groups all Test Case according to its key |
| Reset filtering and sorting | Resets filtering and sorting to default settings |
The grid content could be downloaded as a .csv file.
Test Cases execution - grouped by day charts
The charts show Test Case execution in the last days with the specified resolution. They could be downloaded as a .png file.
Test Cases statistic charts
The pie charts present all Test Cases' statuses (left) and the Test Case resolutions (right) of done TCs. They could be downloaded as a .png file.
Bug metrics
Bugs group by priority
The table presents all bugs reported during tests split between priorities and statuses.
| Column | Description |
|---|---|
| Status | Bug status |
| Priority | Bug priority |
| Quantity | Numer of found bugs. |
| Issue List | List of found bug keys. You can go to that issue page by clicking on it. |
Additionally, there are some available actions:
| Action | Description |
|---|---|
| Open bugs | It shows only open bugs |
| Closed bugs | It shows only closed bugs |
| All bugs | Shows all bugs |
| Show summaries | On the issue list, there are shown the summaries of the issues |
| Hide summaries | On the issue list, there are shown the keys of the issues |
The grid content could be downloaded as a .csv file.
Bugs history
The table contains a history of all connected bugs.
| Column | Description |
|---|---|
| Creation Date | Bug creation date |
| Bug | Bug key. You can go to that page by clicking on it. |
| Summary | Bug summary |
| Priority | Bug priority |
| Status | Bug status |
| Resolution | Bug resolution |
| Resolution Date | Date of setting bug resolution |
The grid content could be downloaded as a .csv file.
Bugs created and resolved chart
A chart that shows all bugs created and resolved for the last days. It could be downloaded as a .png file.
Bugs created and resolved cumulative chart
A chart that shows the number of all bugs created and resolved for the last days. It could be downloaded as a .png file.
Bugs statistic charts
The pie charts present the statuses (left) and the priorities (right) of all Bugs. They could be downloaded as a .png file.
Test Coverage Metrics
Test coverage grid
The table contains all requirements connected to Test Case requirements in a current Test Plan.
| Column | Description |
|---|---|
| REQ ID | Requirement key. You can go to that page by clicking on it. |
| Summary | Requirement summary |
| Priority | Requirement priority |
| Status | Requirement status |
| TC Progress | Current Requirement progress. It shows graphically various Test Case statuses connected to that Requirement. |
| Total | The number of all Test Cases connected to the Requirement. |
| TC Passed | The number of passed Test Cases. |
| TC Failed | The number of failed Test Cases. |
| TC Blocked | The number of blocked Test Cases. |
| TC Skipped | The number of skipped Test Cases. |
| TC None | The number of Test Cases without resolution. |
| Bug Open | The number of unique unresolved Bugs reported to connected Test Cases. |
| Bug Total | The number of unique Bugs reported to connected Test Cases. |
The red rows represent the Requirements connected to Test Plan but not related to any Test Case.
The grid content could be downloaded as a .csv file.
Requirements statistics charts
The pie charts present the requirements connection. The left one shows the ratio between requirements connected to any Test Case and that they haven't any connections. The right presents the ratio between test cases connected to any Requirements and the disconnected. They could be downloaded as a .png file.
Test Cases execution - grouped by requirements
The column chart shows the Test Case resolutions for requirements connected to the current Test Plan. It could be downloaded as a .png file.
Test Cases execution - grouped by requirements priority
The column chart shows the Test Case resolutions for requirements connected to the current Test Plan, grouped by priority. It could be downloaded as a .png file.
Bugs created vs. resolved - grouped by requirements
The column chart shows the bugs state for requirements connected to the current Test Plan. It could be downloaded as a .png file.
QA Craft Automation Test Runs
The Automation panels are explained in the Test Automation section.
QA Craft Requirements
Here you can find all requirements connected to the current Test Plan. They are shown as a tree, where they are grouped to their epics and projects. If a requirement issue hasn't any epic, you will find it in the last position.
At the top of the panel, there is a possibility to edit your choice. After clicking the button, you will see a pop-up with all projects that have requirements issues - you can choose all the needed requirements there.
Test Team
A test team panel allows building the team responsible for realizing the test process. We assume there is only one Test Leader, but you can choose multiple users for analysis and testing. Thanks to that, you have a whole team in one place.
Available Actions
Create Test Suite
The main additional option for Test Plan is creating subordinated Test Suite. It will show you a traditional Create Issue view with blocked some fields that are filled to connect new TS to Test Plan. The rest of that process is analogical to the typical.
Clone structure
For easier test management, there is the option to clone the QA Craft Structure. You can choose any part of the current Test Plan "children" and clone them to the other project. To do that, follow the steps:
- Choose the destination project.
- If you want to keep existing connections with requirements, check the first checkbox.
- If you want to keep chosen files with the automation test, check the second checkbox.
- Choose which part of the current structure should be cloned. You can select the whole Test Plan with all its children or exclude any unnecessary issues.
- Click Clone to start the process.