Test Case specifies the inputs, execution conditions, testing procedure, and expected results that define a single test to be executed.
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.
A custom field that presents a ratio between steps statuses.
A custom field where you can describe the users' roles.
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.
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.
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).
Test Plan Flag
A custom field with a flag that shows if a parent Test Plan is configured for automation tests.
The Steps panel described the whole manual test process. It allows managing all steps from start to finish. The table contains:
|Index||The number of a step.|
|Action||Description of the current action.|
|Input||Input arguments needed to test execution.|
|Expected result||The result how the test should end.|
|Status||Step status describes how the tests ended.|
|Comment||Additional comment to the step.|
Additionally, there are some available actions.
|Import||Import steps saved from a .csv file.|
|Export||Export steps to a .csv file.|
|Reset steps||All steps statuses are changed to an initial value (None).|
|All passed||All steps statuses are changed to a Passed.|
|All failed||All steps statuses are changed to a Failed.|
|Edit steps||Turn a table view mode to the edit mode, which is described below.|
|Compact view||Collapse rows to save space on the page.|
|Extended view||Extend the table to see the wrapped values.|
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 Key||Bug key. You can go to that Bug page by clicking on it.|
|Bug Summary||Bug summary|
|Bug Status||Bug status|
|Bug Resolution||Bug resolution|
|Created||Date when a bug was created|
|Bug Priority||Bug priority|
|Test Case Key||Test Case Key. You can go to that TC page by clicking on it.|
|Test Case Summary||Test Case summary|
|Iteration||Test Case iteration|
|Software version||Software 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.
|Iteration||Test Case iteration|
|Resolution||Test Case resolution|
|Date||Test Case execution date|
|Software ver||Software version|
The Steps History panel presents all changes in Steps since TC creation, including statuses.
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.
That operation allows creating a relation between the current Test Case and chosen Requirement. There can be only one requirement connected to TC.
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.