Features

• Definition and management of test cases
  Single test cases are represented by standard JIRA issues extended with test steps and test parameters.
  This way you can organize your tests just like any other issue using the available data fields, issue operations, labels, issue links, etc. provided by JIRA.
  Additionally you can further organize your tests in a tree structure individually for every project.

• Creating test plans
  T4J provides extensive features for creating and structuring test plans making it easy to model 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 provides execution statistics and reports.

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

• Coverage
  Since tests in T4J are extended 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 and link them to uncovered issues directly from the coverage view. 

Process

The full T4J process consists of the four steps Test Definition, Test Plans, Test Executions and Test Coverage.

These four steps are the main concepts of Test for JIRA and each contain various subtasks.
Although the process includes these steps, you don't have to use all of them. They should be seen as guidelines rather than set specifications.
This makes it easy to integrate T4J with existing testing processes as well as using it for implementing a new one.

A test process in T4J can be as simple as creating a single test, executing it and tracking the result.
Or you can create a more complex test process using the possibility to structure your test projects,
create test plans representing more complex test scenarios, execute them and track the coverage of your requirements.
In T4J it's equally easy to implement. 

Test Definition

Tasks:

• Creating tests that represent single test cases.

• Using the definition tree of a test project to organize the tests used in this project.

• Creating test steps and parameters.

Structuring tests 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 that are needed in test plans to the definition tree of the project.
Note that you don't have to use to definition tree since you can also add tests to a test plan that aren't part of a definition tree.

Test steps and parameters can be added to a test via its Issue Detail View. This view can be accessed through the definition tree.
Therefore a test has to be part of at least one definition tree to manage its test steps and test parameters.
Note that you don't have to specify test steps and parameters for a test step to add it to a test plan or execute it. 

Test Plans

Tasks:

• Creating test plans.

• Structuring 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.
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. 

Test Execution

Tasks:

• Create and run executions.

• Track execution statistics.

Executions can be created from the execution view, they can also be created right from a plan or definition tree.
They 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 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 issue is covered by a corresponding test

• every failed test is covered by a corresponding issue

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