January 26, 2017

JiTest Administration Manual

JiTest Administration Manual

for JiTest v1.7, V2.0


(v 1.7.0, 170126)


  1. Overview of JiTest’s issue types
  2. How to create a new JiTest project
  3. How to add JiTest to an existing SCRUM / Software project
  4. How to add JiTest to other projects
  5. Internal structure / linking of JiTest issues
  6. REST API of JiTest







JiTest introduces a set of new test specific issue types to JIRA

 JiTest is the issue type to use to define test cases

 JiTestsuite is the issue type to group test cases into groups and define a logical structure

 JiTestplan allows to define a set of test case or suites that should be executed in a test run together

 JiTestexecution stores the results of running a test case within the execution of a specific test plan.

 JiTestreports are created when a test plan gets executed at a specific point in time and contains references to all execution issues.


Please note that for Plans to be executable you need to have Version/Releases defined within your project







How to create a new JiTest project

admin-screen01If your software development process asks for a separate project to be created for managing test cases, suites, plans, executions and reports than you can take the short cut and create a new project using the top navigation JiTest menu drop down:

Note that administration rights are required for this operation to be available.









How to add JiTest to an existing SCRUM / Software project

First you need to add all JiTest issue types to your project by going to:

Admin → Projects → “Your Project” → Issue Types (in the left sidebar) → Edit → Add all (JiTest issue types)

In order to be able to work with JiTest you need to add two more fields to the default issue screen:

Admin → Issues → Screens (in the left sidebar) → SCRUM default issue screen → add JiTestParentSuite and Affects Version

Voila your team can start using JiTest within your existing project







How to add JiTest to other projects

It is fairly the same approach as for SCRUM or software projects with the addition that you must also add/create a Bug issue type so that bugs can be reported via the executions issue page and create a new issue type called “Story” which should be used as requirement issue, test cas4es and plans can be linked to, via JiTest’s custom field “JiTRequirement”.







Internal structure / linking of JiTest issues

The picture below shows the internal linking and custom fields used by JiTest to ensure consistency between the different issue types.










REST API of JiTest

JiTest also provides a sophisticated REST API to allow automated tests to be run and results being imported to JIRA JiTest projects. On Request we can provide you with a preliminary Swagger YAML file documenting all the endpoints and parameters used. Alternatively you can check out our online Rest API documentation based on worlds best Swagger tool.

JiTest’s REST API is quite slim as per design JiTest makes outermost usage of JIRA’s features wherever reasonable and possible. Thus creating and modifying JiTest issues can be done with normal JIRA REST API. For comfort reasons we have added some more methods that allow to deal with test management actions more easily.