Versions Compared

Version Old Version 6 New Version 7
Changes made by

David Sedlock

Angelica Salazar

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Panel
titleContents

Table of Contents

...

Basic Navigation

...

Overview

The major tasks for managing test coverage views in T4J 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.

...

Test Coverage - Operations

Display test executions column

The Execution Status column display can be manipulated for each coverage column added. When enabled, this column shows the last execution result(s) for each test in the previous column configured.

The Execution Status column header provides the total number of tests that have either Passed or Failed an execution – or have not been executed at all. Each column cell provides the last executions status and date(s) for the tests in the previous column. (info) Test executions across all projects will show in this column.

Show last execution results for specific test definitions

The following steps will configure a coverage view that shows the last execution result(s) for specific test definitions.

  • Switch to the coverage view of the project you want to monitor.
  • Click Select Source Items.
  • Give a Label for the new column. For Example, Test Definitions.
  • Select Issue Types, Filter or JQL to select issues which will show up in the coverage view.
  • Fill the selection criteria accordingly. (info) The selection should ideally contain only test definitions. 
  • Tick the checkbox to Display Test Executions Column and input the desired number of executions to be displayed. By default, executions done on the test case from <all> projects will be displayed. To filter the executions further to only desired projects, select project(s) from the project dropdown.
  • Click Select.

The first column of the coverage will show all issues that match the selected criteria. The second column will show the last execution result(s) for the selected issues.

Show last execution results for specific issues that have test definitions linked

The following steps will configure a coverage view that shows the last execution results for issues that have test definitions linked. It assumes, that a the JIRA project is configured in such a way that issues which need testing are properly linked to their according test definitions.

  • Switch to the coverage view of the project you want to monitor.
  • Click Select Source Items.
  • Give a Label for the new column. For Example, User Stories.
  • Select Issue Types, Filter or JQL to select issues which will show up in the first column of the coverage view.
  • Fill the selection criteria accordingly. (info) The selection should only include user stories, bugs or similar issue types which have test definitions linked.
  • Click Select.
  • Click Add Coverage Level.
  • Give a Label for the new column. For Example, Test Definitions.
  • Select Issue Types, Filter or JQL to select test definitions which will show up in the second column of the coverage view. (info) A useful selection could be Issue Types together with the issue type Test Case.
  • Select one or more link types in the field Link Types. (info) It may be useful to have a custom link type tested by which will be used to interconnect user stories and bugs with their according test cases.
  • Tick the checkbox to Display Test Executions Column and input the desired number of executions to be displayed.
  • Click Add.

The first column of the coverage will show all source issues that match the selected criteria. The second column will show all test definitions that are linked to the source selection matching the selected link types. If a source issue is not linked to a corresponding test, it will be visible in the coverage view. The third column will show the last execution result(s) for the test definitions of the second column.

Create issue for column

  1. Create a coverage view with at least two columns excluding the test result column.
  2. Click the Three Dot icon inside of a cell to open an inline dialog.
  3. Select a link type for the new issue and click Create issue.
  4. Fill the default JIRA dialog for new issues and click Create.
  5. The Coverage view updates accordingly and takes the new issue into account. (info) Be aware, that the issue will only show up in the configuration if it matches the columns criteria.

Remove coverage column

  1. Load a coverage configuration or configure a new coverage view with at least two columns excluding the result column.
  2. Click The Remove icon in the heading of the coverage column you wish to remove. (info) The remove icon is not available for source selection, because a source selection is needed for every configuration. Use the Update icon for source selection instead.

Edit coverage column

  1. Load a coverage configuration or configure a new coverage.
  2. Click The Update icon in the heading of the coverage column you wish to edit.
  3. Edit the column data according to the new requirements and click Update.

Save coverage configuration

  1. Configure a new coverage view.
  2. Click Save View as in the top left corner.
  3. Fill a Name for this coverage configuration.
  4. Select if the view should be Public and available for all T4J users or Private and only available for the current user.
  5. Click Save.

Load and modify coverage configuration

The following steps assume that a coverage view previously got saved.

  1. Click a previously saved coverage on the left sidebar.
  2. Edit the coverage configuration according to the new requirements.
  3. Click Save View to save the current configuration. (info) Please be aware, that the previous configuration will be overwritten. Select Save View as from the dropdown next to the button to save to separate configuration instead.

Rename or delete coverage configuration

The following steps assume that a coverage view previously got saved.

...

    • You should now see the definition view, which is the default view of a project.

  • Select the Coverage entry in the main T4J 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.

Table of Contents
minLevel1
maxLevel7

Coverage View Tasks

Task

Action

Create Coverage View

  • If there is no active coverage view, select the button “Select Source Items”. If a coverage view is displayed, first select the button “Clear All” and then select “Select Source Items”.

  • Provide the information in the dialog “Select Source Items” - see task “Specify Coverage Level”.

  • Select “Save View As” in the left column, providing a name for the view and specifying whether the view is for your use only (private) or shared with others (public).

Add Coverage Level

  • Select the button “Add Coverage Level”.

  • Provide the information in the dialog “Add Coverage Level” - see task “Specify Coverage Level”.

  • Select “Save View” in the left panel.

Edit Coverage Level

  • Select the Edit icon in the header of a column.

  • Provide the information in the dialog “Update Coverage Level” or “Update Source Items” - see task “Specify Coverage Level”.

  • Select “Save View” in the left panel.

Remove Coverage Level

  • Select the Remove icon in the header of a column. The view is immediately removed, without confirmation.

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:

  • Label: The title of the column.

  • Source: Select one of the following options to determine how the issues in the column are to be identified. The input field above this item changes to reflect the choice of option.

    • Issue Types - You will specify one or more issue types in the input field.

    • Filter - You will select the name of a saved Jira query in the input field.

    • JQL - You will provide an expression in the Jira Query Language in the input field.

  • Link Types: In the case of the “Add Coverage Level” and “Update Coverage Level” dialogs, this additional option is displayed, in which you specify the link types that are used to determine the relationship between issues in the column and issues in the preceding column. See section How to Specify Link Types for more about this.

  • Test Executions: If the issues in the column are test cases with test executions, select this option to add an extra column showing recent test executions of the cases. You can specify the number of executions to be shown.

  • Project Name: By default, related test executions can be in any project, but you can limit this by specifying one or more projects here. Note that the projects specified here have nothing to do with projects of the issues to be included in the column being defined.

Refresh Coverage View

  • Select the button “Refresh” to rerun all queries and bring the view up to date with Jira.

Determine Display Fields

  • Select the button “Display Fields” to add additional fields to the information displayed about each issue.

Export Coverage View

  • Select the button “Export” and choose the option “XML” or “Excel” to determine the export format.

Copy Coverage View

  • Select Save View as from “…” next to the name of the active view. Provide a name for the new view and choose whether it is private or public.

Rename Coverage View

  • Select Rename using the triangle next to the name of a view and provide a new name for the view.

Delete Coverage View

  • Select Delete using the triangle next to the name of a view.

Get Link to Coverage View

  • Select Get URL using the triangle next to the name of a view. The resulting link can be shared with someone via email.

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.

Info

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.