5.4.
Test Cases
|
||
|---|---|---|
 | Chapter 5. Define |  |
| 5.4.
Test Cases
|
||
|---|---|---|
| | Chapter 5. Define | |
A test case is a set of input values, execution preconditions, expected results and execution postconditions, developed for a particular objective or test condition, such as determine whether an application or software system meets its specifications or not.
The Maintain Test Cases page allows to create, edit, remove, clone and search test cases. This is done by editing the table of the Maintain Test Cases page shown in Figure 5.10
By clicking into of the fields of the table the most important values of a test
case (
Name
,
Traceability
,
Priority
,
State
and
Execution)
can be edited directly by clicking in the input field in the table.
More attributes of a
test case and its steps can be edited in a
detailed page by clicking on the
Edit
icon (
Section 5.4.1.4, “Edit Test Case”
).
Press the
button to submit the changes that have been made
or the
button
to discard.
![[Note]](images/note.png) | Warning Sign in the ID Column |
|---|---|
|
A
test case with execution set to manual containing no steps is not executable. To
indicate this, a
warning sign (
|
By clicking on the
button the user is able to create a new test case
(
Figure 5.10
)
. An empty row is added at the beginning of the table. The fields
Name
,
Traceability
,
Priority
,
State
and
Execution
of the test case can be specified.
The test case ID is automatically assigned by Klaros-Testmanagement.
The project is the
current selected project.
To set more properties the user may click
on the
Edit
icon (
Section 5.4.1.4, “Edit Test Case”).
To create a copy of the test case press the
clone icon.
Press the
button to confirm the creation or the
button
to discard the changes. The user can create and save
more than one test case at
time.
![[Important]](images/important.png) | Klaros-Testmanagement Enterprise Edition Feature |
|---|---|
|
This feature is only available in the Klaros-Testmanagement Enterprise Edition. |
If there user defined properties for test cases configured, they can be edited on this tab. Figure 5.11 )
| Note |
|---|---|
|
The tab is disabled if no user defined properties for test cases exist. How to maintain the user defined properties is decribed in section Section 5.1.2.8, “Editing the user defined properties of a project” . |
It is possible to search for test cases and sort the results of the search with the filtering and sorting options. The filtering and sorting options become visible by opening the Filter / Sort panel. The Filter / Sort panel contains two tables. The left table contains the filtering parameters, the right table contains the sorting parameters.
Below the two tables you find two buttons:
|
|
The button applies the filter and sorting criteria specified in the two tables above and presents the filtered and sorted result in the table below. |
|
|
The button clears the tables with the filter and sorting criteria and displays all test cases. |
Each line in the filter table represents a criterion that restricts the result set that is displayed in the table below, i.e. the set of all test cases is filtered for the conjunction of all criteria listed in the filtering table.
By
clicking the
button, a new and empty row for a filter criterion is appended to the table. The
table with the
filtering criteria has
four columns:
The Field column denotes the field in the table that the criterion is filtering for. In the Filter / Sort panel of the maintain test cases page are eighteen fields that can be filtered: ID, Name, Description, Traceability, Priority, State, Execution, Team, Type, Area, Level, Variety, Docbase, Dependency, Note, Evaluation, Precondition and Postcondition.
The Type column denotes the operator that is used for the criterion. In the maintain test cases page the following operators are available:
|
Equals |
Only the items that exactly match the value of the criterion are shown. |
|
Not equals |
The items that do not equal the value of the criterion are shown in the result table. |
|
Greater than or equals |
Items that are greater than or equal the value of the criterion are shown. |
|
Less than or equals |
Items that are less than or equal the value of the criterion are shown. |
|
Greater than |
Items that are greater than the value of the criterion are shown. |
|
Less than |
Items that are less than the value of the criterion are shown. |
|
Like |
Items that have a part that matches value of the criterion are shown. |
The Value column defines the value for the filtering criterion.
The
Action
column contains a button (
)
for deleting the criterion in the current line.
The table that contains the list of test cases can be sorted. The criteria for the sorting are specified in the right table in the Filter / Sort panel. It is possible to specify more than one sorting option. If there are more than one sorting options the uppermost sorting criterion has the highest priority, lowest row in the sorting criterion table has the lowest priority.
When the
button is clicked, a new empty row for a sorting criterion is appended at the
bottom of the
sorting options table. Each row in the sorting options table has in
the
Action
column a
button (
).
By pressing this button the row with the sorting criterion
can be removed.
The sorting options table contains three columns:
The Order By column denotes the field in the results table that the sorting applies to. The fields that can be sorted for in the maintain test cases screen are ID, Name, Description, Traceability, Priority, State, Execution, Team, Type, Area, Level, Variety, Docbase, Dependency, Note, Evaluation, Precondition and Postcondition.
The Type column defines the direction of the sorting sequence, i.e. descending or ascending.
The Action column contains a button for deleting the sorting criterion.
By clicking the
Edit
icon the view will change (
Figure 5.12
) and
offers the possibility to change the following attributes:
ID
Assigned automatically
Revision
Assigned automatically and incremented every time a test case is changed
Team
The team that executes the test case
Name
The name of the test case allocated
Description
A brief description of the test case
The preconditions of the test case means everything that is necessary to execute a test case, e.g. "It is necessary to have a database with valid data.".
The postcondition defines the criteria that must be fulfilled after the test case has been executed, e.g. the postcondition of a successful login test case is that the user is authenticated and the home page of the application appears.
Area
The requirements to cover by the test case
Design Technique
The method of execution: Black-Box or White-Box
Variety
The expected behave of the test run: Positive or Negative
Level
The test stage(s) of the test case, for example unit tests or system test
Priority
The priority of the test case: Low, Medium or High
Docbase
Reference to the document base of the test case, which contains the requirements of the test case
Note
An additional note for the test case, contains outside information of the test case that maybe useful for users to know
Dependency
The dependencies of the test case (another test case)
Evaluation
The mode of the result evaluation: Manual or Automatic
Execution
The mode of execution of the test case: Manual or Automatic
Traceability
A reference to the corresponding use case or work package
State
Only test cases with the state Draft are editable. To edit a test case you have to change and save the state to Draft first. A Locked test case is not executable and a Skip test case is not shown in any reports. If the test case is approved then set the state to Approved .
Press the button to get an empty form for a new test case. All the data changed in the previous form is discarded.
Press the button to submit the changes that have been made or the button to discard the changes.
| What is to do to create a new revision of the test case? |
|---|---|
|
To create a new revision of the test case the checkbox Create new revsion? must be selected. |
By clicking on the
Delete
icon the test
case will be removed from Klaros-Testmanagement
database.
![[Warning]](images/warning.png) | Warning |
|---|---|
|
Only test cases that are not referenced by results or test suites can be deleted. |
By clicking on the Steps tab a page will be shown that offers the possibility to change the following attributes:
Condition that must be fulfilled before the execution of the test case, e.g. "The user is not yet logged in."
Action
The test action, e.g. "Enter name and password, and click button Login."
Condition that must be fulfilled after the execution of the test case, e.g. "The user is authenticated and has access to the system."
| Why is the Steps tab disabled? |
|---|---|
|
The purpose of test steps is the guidance of a tester through a manual test. So steps are only sensible for manual tests. Because of this, the "Steps" tab is only enabled if the "Execution" field is set to "Manual". |
To
change the order of the test steps use the
or
icons.
Press the button to create a new test step, the button to return to the test cases view or the button to discard the changes.
By clicking on the
Delete
icon the test step will be removed from Klaros-Testmanagement
database when the user save the test case changes clicking on the
button in
Figure 5.12
.
By clicking on the Attachments tab a page will be shown that offers the possibility to add attachments to the test case. the button opens the "open file dialog". The button uploads the file to Klaros-Testmanagement.
After
the attachment is saved to the test case, it is possible to download
the file by
clicking on the
icon.
By
clicking on the
icon the attachment
will be removed from Klaros-Testmanagement
database when the user saves the test case changes clicking on the
button.
By clicking on the Revisions tab a page will be shown that shows the revisions history of the test case.
| Warning |
|---|---|
|
The tab is only enabled if the test case has a revisions history to show. |
By clicking on the name link of the test cases, it is possible to browse and compare the revisions.
| |  | |
5.3.
Maintaining Systems Under Test
|  | 5.5.
Test Suites
|
