Test Coverage - How-to Guide
Overview
The major tasks for managing test coverage views in easeTest are explained in the sections below. To work on a coverage view, the first step is to navigate to it, as follows:
Select the project to open, using one of the following ways:
Select Tests in the main navigation bar and select a project from Current Project or Recent Projects.
Select Tests > View all projects from the main navigation bar and select a project from the list.
You should now see the definition view, which is the default view of a project.
Select the Coverage entry in the main easeTest menu. You should now see the Coverage View, which displays the name of the active view followed by a list of existing views in the left panel. The views are organized into two lists:
Personal views, which only the user who created them can access.
Public views, which have been shared with others.
To work on a specific view, select the name of the view in the left panel.
Operations
Task | Action |
---|---|
Create Coverage View |
|
Add Coverage Level |
|
Edit Coverage Level |
|
Remove Coverage Level |
|
Specify Coverage Level | The dialogs “Select Source Items”, “Update Source Items”, “Add Coverage Level” and “Update Coverage Level” are used to specify the contents of a coverage level column, according to the following information:
|
Refresh Coverage View |
|
Determine Display Fields |
|
Export Coverage View |
|
Copy Coverage View |
|
Rename Coverage View |
|
Delete Coverage View |
|
Get Link to Coverage View |
|
How to Specify Link Types
Issues may be related to each other in various ways, using different so-called “link types” in Jira. A link type relates two issues, A and B, and has two directions, A → B and B → A. If the intention is that the relation is not symmetrical, the directions have different so-called “inward” and “outward” descriptions in Jira.
In the following example, we assume that you link requirements to test cases with the link type “Test” and the direction from requirement to test case (called “inward”) is described as “is tested by” and the direction from test case to requirement (called “outward”) is described as “tests”. That is, a given requirement is tested by a given test case, while the test case tests the requirement.
Now if the first column in your table is for customer requirements and the next column is for test cases, then you would specify the description “is tested by” in order to exclude other kinds of links that might exist between the issues.
Notice that the description of the link type is determined from the point of view of issues in the first column and is the so-called “inward description” of the link type. In this example, the “outward” description of the link type (“tests”) would be the wrong name to specify.