Page tree
Skip to end of metadata
Go to start of metadata



Test Case specifies the inputs, execution conditions, testing procedure, and expected results that define a single test to be executed.

Dedicated fields

Test Suite

A custom field that keeps a handle to the "parent" Test Suite.


A custom field that keeps a handle to connected Requirement.

Test Case Type

A custom field that determines the type of test case. You can choose between Manual and Automation tests.


A custom field where you can describe test preconditions.


A custom field that keeps a current iteration number.

Steps progress

A custom field that presents a ratio between steps statuses.

User roles

A custom field where you can describe the users' roles.

Test Result

A custom field where you can describe the results of the tests. You can set a value when you end the test.

Test Case Execution

A custom field with a flag that shows if a Test Case can be executed. You can choose between Blocked and Unblocked.

Test Environment

A custom field that presents the test environment. You can choose between Production, Preproduction and Testbed. To edit options, go to Test Environment issue type configuration.

Software version

A custom field where you can set tested software version.

Test Case Resolution

A custom field that keeps a result status after tests. You can choose between Passed, Failed, Blocked, Skipped and None (for tests before or in progress).

v <4.0.400

Test Plan Flag

A custom field with a flag that shows if a parent Test Plan is configured for automation tests.

Available Panels



The Steps panel described the whole manual test process. It allows managing all steps from start to finish. The table contains:

IndexThe number of a step.
ActionDescription of the current action.
InputInput arguments needed to test execution.
Expected resultThe result how the test should end.
StatusStep status describes how the tests ended.
CommentAdditional comment to the step.

Additionally, there are some available actions.

ImportImport steps saved from a .csv file.
ExportExport steps to a .csv file.
Reset stepsAll steps statuses are changed to an initial value (None).
All passedAll steps statuses are changed to a Passed.
All failedAll steps statuses are changed to a Failed.
Edit stepsTurn a table view mode to the edit mode, which is described below.
Compact viewCollapse rows to save space on the page.
Extended viewExtend the table to see the wrapped values.

Edit steps

In the edit view, there is a possibility to edit any values that the table contains. You are also allowed to add the new steps or remove existing ones. All changes can be saved or canceled.

You can't edit or import the steps of resolved Test Case.

When you double-click on the value, there will be shown an edit form like that:

Besides classic operations like submitting, resetting or canceling changes, you can also choose a file from the issue's attachments and connect it to the selected value.

Automation Tests Steps


You are allowed to show a file that specifies the automation test. When you click on the path, you can choose the file. Below you can see its preview.

Bugs linked to the Requirement

The table presents all open Bugs related to the same requirement and various Test Cases.

Bug KeyBug key. You can go to that Bug page by clicking on it.
Bug SummaryBug summary
Bug StatusBug status
Bug ResolutionBug resolution
CreatedDate when a bug was created
Bug PriorityBug priority
Test Case KeyTest Case Key. You can go to that TC page by clicking on it.
Test Case SummaryTest Case summary
IterationTest Case iteration
EnvironmentTest environment
Software versionSoftware version

TC Resolution History

The table contains a whole Test Case execution history. The new rows will be added with iteration after setting a resolution.

IterationTest Case iteration
ResolutionTest Case resolution
DateTest Case execution date
Software verSoftware version

Steps History


The Steps History panel presents all changes in Steps since TC creation, including statuses.

Available Actions

Create Bug

The main additional option for the Test Case is creating subordinated Bug. It will show you a traditional Create Issue view with blocked some fields that are filled to connect the new Bug to Test Case. The rest of that process is analogical to the typical.

Add Requirement

That operation allows creating a relation between the current Test Case and chosen Requirement. There can be only one requirement connected to TC.

Remove Requirement

There is also a possibility to remove relation to a Requirement. Choose that option will require your confirmation.

Add to structure

That operation allows connecting the current Test Case to any Test Suite. If the TC is an orphan, it will be connected to the new parent. In the other case, its parent will be changed.

Disconnect from structure

There is also a possibility to detach the Test Case from the structure. Choose that option will require your confirmation.

  • No labels