Page tree
Skip to end of metadata
Go to start of metadata

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:

ColumnDescription
TSTest Suite key. You can go to that TS page by clicking on it.
TS NameTest Suite summary
TS PriorityTest Suite priority
TS ProgressCurrent Test Suite progress. It shows graphically various Test Case statuses connected to that Test Suite.
TC PassedThe number of passed Test Cases. You can list them by clicking on them.
TC FailedThe number of failed Test Cases. You can list them by clicking on them.
TC BlockedThe number of blocked Test Cases. You can list them by clicking on them.
TC SkippedThe 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 TotalThe number of all Test Cases connected to the Test Suite. You can list them by clicking on them.
BUG OpenThe 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 TotalThe 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 TotalThe 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.

ColumnDescription
DateDate when the Test Cases was executed.
Total TCThe number of all executed Test Cases. You can list them by clicking on them.
PassedThe number of passed Test Cases. You can list them by clicking on them.
FailedThe number of failed Test Cases. You can list them by clicking on them.
BlockedThe number of blocked Test Cases. You can list them by clicking on them.
SkippedThe 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.

ColumnDescription
Execution DateDate when the Test Cases was executed.
Test CaseTest Case key. You can go to that TC page by clicking on it.
SummaryTest Case summary
IterationThe current Test Case iteration
VersionSoftware version
EnvironmentTest environment
StatusTest Case resolution
RequirementThe 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:

ActionDescription
Show current iterationsHides previous Test Case iterations when they are visible
Show all iterationsShows all Test Case iteration when they are hidden
Group by Test CaseGroups all Test Case according to its key
Reset filtering and sortingResets 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.

ColumnDescription
StatusBug status
PriorityBug priority
QuantityNumer of found bugs.
Issue ListList of found bug keys. You can go to that issue page by clicking on it. 

Additionally, there are some available actions:

ActionDescription
Open bugsIt shows only open bugs
Closed bugsIt shows only closed bugs
All bugsShows all bugs
Show summariesOn the issue list, there are shown the summaries of the issues
Hide summariesOn 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.

ColumnDescription
Creation DateBug creation date
BugBug key. You can go to that page by clicking on it. 
SummaryBug summary
PriorityBug priority
StatusBug status
ResolutionBug resolution
Resolution DateDate 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.

ColumnDescription
REQ IDRequirement key. You can go to that page by clicking on it. 
Summary

Requirement summary

PriorityRequirement priority
StatusRequirement status
TC ProgressCurrent Requirement progress. It shows graphically various Test Case statuses connected to that Requirement.
TotalThe number of all Test Cases connected to the Requirement.
TC PassedThe number of passed Test Cases.
TC FailedThe number of failed Test Cases.
TC BlockedThe number of blocked Test Cases.
TC SkippedThe number of skipped Test Cases.
TC NoneThe number of Test Cases without resolution.
Bug OpenThe number of unique unresolved Bugs reported to connected Test Cases.
Bug TotalThe 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:

  1. Choose the destination project.
  2. If you want to keep existing connections with requirements, check the first checkbox.
  3. If you want to keep chosen files with the automation test, check the second checkbox.
  4. 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.
  5. Click Clone to start the process.
  • No labels