6.4.
Test Cases
|
||
|---|---|---|
 | Chapter 6. Define |  |
| 6.4.
Test Cases
|
||
|---|---|---|
| | Chapter 6. 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 in order to determine whether or not an application or software system meets its specifications.
The Maintain Test Cases section allows the creation, removal, cloning and updating of test cases, searching through all of the test cases in the selected project and the assigning of test cases to categories ( Figure 6.10 ). All of this can be done through the tabular view or on the details page.
The
Maintain Test Cases
screen shows a table with all of the test cases defined for the current project.
Each
row of the table represents a test case, the columns represent attributes of
the test
case.
Clicking on the fields of the table allows the most important values of a test
case (
Name
,
Traceability
,
Priority
,
State
and
Execution)
to be directly edited.
More attributes of a
test case and its steps can be edited in a
detailed page by clicking on the
Edit
icon (
Section 6.4.1.5, “Edit Test Case”
).
The selection column allows test cases to be selected and group actions to be carried out. The checkbox in the title bar of the table is a global select button, which allows bulk actions to be carried out for all test cases that match the current search criteria and, if categorization is enabled, are in the currently selected category.
The bulk actions available on the Maintain Environments screen are: Delete, Clone, Create New Revisions, Create Test Suite From Test Cases and Assign to category (Klaros-Testmanagement Enterprise Edition only). The bulk action buttons can be found above the table on the left.
Clicking the button submits the changes that have been made and clicking the button discards them.
![[Note]](images/note.png) | Warning Sign in the ID Column |
|---|---|
|
A
test case which has execution set to manual and contains no steps is not executable.
To
indicate this, a
warning sign (
|
Clicking the
button enables the user to create a new test case
(
Figure 6.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 test case is assigned to the
current selected project.
Clicking the
Edit icon allows the user to set more properties (
Section 6.4.1.5, “Edit Test Case”)
And Clicking the
clone icon allows the user to create a copy of the test case.
Clicking the
button confirms the creation of the test case and clicking the
button
discards the changes. The user can create and save
more than one test case at a
time.
If there are user-defined properties for test cases configured, they can be edited in this tab. Figure 6.11 )
| Note |
|---|---|
|
This tab is disabled if no user defined properties for test cases exist. The maintenance of user defined properties is described in Section 6.1.1.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 table on the left contains the filtering parameters, while the table on the right contains the sorting parameters.
Below the two tables are 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 projects. |
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. The fields which can be filtered in the Filter / Sort panel of the maintain test cases page are ID, Name, Description, Traceability, Priority, State, Execution, Team, Type, Area, Level, Variety, Docbase, Dependency, Note, Evaluation, Precondition and Postcondition , as well as any user-defined properties. The process of maintaining the user-defined properties is described in section Section 6.1.1.8, “Editing the user-defined properties of a project” . User-defined properties are only available in Klaros-Testmanagement Enterprise Edition.
The Type column denotes the operator that is used for the criterion. The following operators are available on the maintain test cases page:
|
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 is more than one sorting option, the uppermost row in the sorting criterion table has the highest priority and the lowest row 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 on the maintain test cases page are ID, Name, Description, Traceability, Priority, State, Execution, Team, Type, Area, Level, Variety, Docbase, Dependency, Note, Evaluation, Precondition and Postcondition , as well as any user-defined properties. The process of maintaining the user-defined properties is described in section Section 6.1.1.8, “Editing the user-defined properties of a project” . User-defined properties are only available in Klaros-Testmanagement Enterprise Edition.
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.
![[Important]](images/important.png) | Klaros-Testmanagement Enterprise Edition Feature |
|---|---|
|
This feature is only available in Klaros-Testmanagement Enterprise Edition. |
The categorization panel contains some artifacts which help to group test cases together, the Category Group and the Category . Test environments may be assigned to one category in each category group. There is no limit on the amount of categories or category groups which may be created.
Using Categorization, it is possible to group test cases in user-defined categories. In order to activate categorization, the Categories panel must be opened. The Categories panel contains 3 different views, the Edit view, the Tree view and the Menu view. If no categories have been defined, only the edit view may be used. Each view allows selection of the active category group through the use of a dropdown menu, or selection of the blank category group to disable categorization.
This view allows the creation and naming of category groups and categories, as
well as
the organization of category heirarchies. Pressing the
button at the top of this view creates a new category group, and enables the use
of
the category group dropdown menu. If a category group is selected, it may be
renamed
in this view. Categories may also be added as sub-categories of the group's
root
category, renamed, given a description and be nested in a hierarchical manner.
This view shows an overview of the category structure for test cases . The available categories are represented as a collapsible tree, with the name of each category is shown, along with the number of test cases it contains. The description of each category is shown as a tooltip when its name is hovered over with the mouse pointer.
Clicking the
Edit
icon causes the view to change (
Figure 6.12
) and
allows the user to view or change the following attributes:
ID
Assigned automatically
Revision
Assigned automatically and incremented every time a test case is changed
Name
The editable name of the test case
Description
A description of the test case
The precondition of the test case, describing the requirements for executing the test case, e.g. "It is required that the database is initialized."
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 category of requirements that is covered by the test case
Design Technique
The test design view on the system under test: Black-Box or White-Box
Variety
The result expectation of the test: Whether a positive or negative result is expected
Team
The team that is responsible for the test case
Level
The test level of the test case, for example unit, integration or system test
Priority
The priority of the test case: Low, Medium or High
Docbase
A reference to the document this test case is based on, which may e.g. contain the requirements this test case is related to
Note
A note that may contain additional information regarding the test case that maybe useful for users to know
Dependency
The dependencies of the test case (it may depend on another test case)
Evaluation
The mode of test result evaluation: Manual or Automated
Execution
The mode of test case execution: Manual or Automated
Traceability
A reference to the corresponding requirement, use case or work package
State
The test case state determines whether it is editable, executable or visible in result listings. 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 .
Clicking the button submits the changes that have been made and clicking the button discards the changes. Clicking the print icon allows all fields of the test case to be displayed in a single, printer-friendly page( Figure 6.13 ). The print view is only available in Klaros-Testmanagement Enterprise Edition.
| How to create a new revision of a test case? |
|---|---|
|
To create a new revision of a test case the checkbox Create new revision? must be selected. |
Clicking on the
Delete
icon causes the test
case to be removed from the Klaros-Testmanagement
database.
![[Warning]](images/warning.png) | Warning |
|---|---|
|
Only test cases that are not referenced by results or test suites can be deleted. |
Clicking on the Steps tab will cause a page which allows the user to change the following attributes to be shown:
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. For this reason, 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 the
and
icons may be used. Clicking on the
Add
icon causes a new test step to be inserted at the chosen position.
Clicking the button creates a new test step, pressing the button returns to the test cases view and the button discards the changes.
Clicking the
Delete
icon causes the test step to be removed from the Klaros-Testmanagement
database when the user saves the test case changes by clicking on the
button in
Figure 6.12
.
Clicking on the Attachments tab causes a page which offers the possibility to add attachments to the test case to be shown. Clicking the button opens the "open file dialog". Clicking the button uploads the selected 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.
Clicking
on the
icon causes the attachment
to be removed from the Klaros-Testmanagement
database when the user saves the test case changes by clicking on the
button.
Clicking the Revisions tab causes a page which shows the revisions history of the test case to be shown.
| Warning |
|---|---|
|
This tab is only enabled if the test case has a revisions history to show. |
Clicking the relevant row of the Revisions column in the table allows the user to browse and compare the revisions.
| |  | |
6.3.
Maintaining Systems Under Test
|  | 6.5.
Test Suites
|
