Versions Compared

Old Version 5

changes.mady.by.user David Sedlock

Saved on

compared with

New Version Current

changes.mady.by.user Bernhard Doleschel

Saved on

Key

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

Overview

Test Management for JIRA Jira is a native JIRA Jira Server add-on that brings provides extensive test management capabilities to for your project.
It T4J extends JIRA Jira with a set of new views and important features that support testing. These features T4J can be used with any JIRA Jira project.

Table of Contents

Features

  • Definition and management of test cases
    Single test cases are represented by standard JIRA Jira issues extended with test steps and test parameters.
    This way you can organize your tests You can define your test cases just like any other issue using the available issues, using all of Jira’s features: data fields, issue operationslabels, labelslinks, issue linksoperations, etc. provided by JIRA.
    Additionally, you can further organize your tests test cases in a tree structure individually for every project individually.

  • Creating test plans
    T4J provides extensive features for creating and structuring test plans, making it easy to model handle complex test scenarios.

  • Manual test execution
    An execution runner is provided for manually executing single tests and test plans.

  • Automatic test execution
    T4J integrates well with other applications via its REST API.
    This way your application carrying out the actual test executions can transfer the results to T4J which saves the corresponding test definition and test plan data and The test case definitions and test data are managed in Jira, while the actual testing is carried out by a separate testing application. The results are then transferred back to T4J, which provides execution statistics and reports.

  • Export
    Test for JIRA T4J provides features for exporting tests cases, test plans, test case executions and executions execution statistics.
    Almost all standard Standard export formats are supported for export.

  • Coverage
    Since tests test cases in T4J are extended JIRA Jira issues it's easily possible to cover existing project issues with tests.
    T4J provides a view to check the coverage of tests and issues.
    You can create tests , it is easy to link them to other project issues (e.g. requirements or development tasks), thereby establishing coverage. T4J provides views to determine the extent of test case coverage. You can create test cases and link them to uncovered issues directly from in the coverage view itself. 

Process

The full complete T4J process consists of the four steps activities: Test Case Definition, Test PlansPlanning, Test ExecutionsExecution and Test Coverage Evaluation. These four steps activities are the main concepts of Test for JIRA T4J and each contain encompasses various subtaskstasks.
Although the full process ideally includes these stepsactivities, you don't have to use all of them. They should be seen as guidelines rather than set specificationsa rigid process.
This makes it easy to integrate T4J with existing testing processes as well as using it for implementing a new onein your organization.

A test testing process in T4J can be as simple as creating a single test case, executing it once or many times and tracking the resultresults.
Or you can create a more complex test process using the possibility to structure your test projects,
You can extend the test process by structuring test cases hierarchically. You can also create test plans representing more complex test scenarios , execute them and track tracking the coverage of your requirements .
In T4J it's equally easy to implement. by test cases. It is up to you to use the features of T4J to establish a testing process that works for your organization.

Creating tests

Activity

Tasks

Explanation

Test Definition

Tasks:

  • Create issues that represent single test cases.

Using

  • Use the definition tree of a

test

  • project to organize the

tests used in this project

  • test cases.

Creating

  • Add test steps and parameters to the test cases.

Structuring

tests

test cases using the definition tree makes it

easier to later add them to test plans of the same project.
Therefore it's useful and recommended to add all tests

easy to understand the cases and how they fit into the overall project. It also facilitates the creation of test plans in the project. We recommended adding all test cases, or at least those that are needed in test plans, to the project’s definition tree

of the project.
Note

. (But note that you don't have to use

to

a definition tree for test planning, since you can also add tests to a test plan

that

even if they aren't part of a definition tree.)

Info

T4J does not require the use of any special issue types, but using a particular issue type to distinguish test cases from other sorts of issues is a good idea. Therefore, if you do not already have an issue type such as Test Case, we highly recommended having your Jira administrator create it. See Recommended Issue Type for Test Cases.

Test steps and parameters

can be

are added to a test

via its

case in the T4J Issue Detail View. This view

can be

is accessed through the definition tree

.
Therefore a test has to be part of at least one definition tree

, so a test case must appear in the definition tree in order to manage its test steps and test parameters.


Note

(But note that you don't have to specify test steps and parameters

for

to add a test

step to add it

case to a test plan or to execute it.

 

Test Plans

Tasks:

Creating

)

Single test cases can already be executed from the definition tree. Test case parameters can be overwritten when you start the execution.

Test Planning

  • Create test plans.

Structuring

  • Structure the content of test plans using the plan tree.

  • Overwriting test parameters with plan specific values. 

    • It's possible to create test plans that bundle different tests to model bigger test scenarios.

    Test plans are used to bundle different test cases together in order to handle complex test scenarios. (Note that you don't have to create test plans to execute tests.


    It's also possible to directly execute single tests from the definition tree that contains them. 

    ) The test cases in a plan can be organized hierarchically.

    Test Execution

    Tasks:

    • Create test case executions and run

    executions

    • them.

    • Track execution statistics.

    Executions

    Test case executions can be created

    from

    in the execution view,

    they can also be created right from a

    in a test plan or in the definition tree.


    They

    Test cases can be run manually using the execution runner or via the REST API of T4J.


    This workflow step can also include tracking execution statistics via the Execution View or exporting them for use with other applications. 

    Test Coverage

    Tasks:

  • Tracking the coverage of issues

    • Tracking

    Note that test case parameters can be overwrittenduring execution.

    Test execution statistics are available in the Execution View. The statistics can also be exported in different formats.

    Test Coverage Evaluation

    • Track the coverage of requirements or other issues by test cases.

    • View the status of test case executions.

    • Track the coverage of failed tests

  • Covering issues and failed test

    • The coverage can be configured individually using one or many coverage levels.
    This workflow step can be used to make sure that

    every

    • by bugs.

    • Fix coverage gaps by linking test cases to requirements and other issues.

    • Fix gaps in execution failure coverage by linking bugs to test cases.

    The Coverage View is used with the goal of ensuring that:

    • Every requirement or issue is covered by a corresponding test

    every failed test

    • case.

    • Every execution failure is covered by a corresponding

    issueThis workflow step also includes covering uncovered tests and issues.
    Note that all previous workflow steps work independently from the test coverage

    • bug.

    The view allows you to determine the degree to which these goals are achieved, allowing the project to identify and fix weak points in testing.

    The Coverage View optionally provides information on the execution of test cases - for example, whether the latest execution status is pass or fail.

    Coverage views can be configured individually, using as many coverage levels as make sense in the project.