Table of Contents
This chapter describes how to execute test cases and test suites, how to continue unfinished test suite executions and finally how to create issues for tests that failed.
Executing a test case consists of running a test on a specific version of the SUT in a selected test environment.
The Run a Single Test Case page shows all test cases in a list. To get a better overview about the available test cases the sorting and searching functionality of the Filter / Sort panel can be used.
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 Run A Single Test Case 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 Run A Single 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 is sorted for. The fields that can be sorted for in the Run Single Test Case 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.
To execute a
test case click on the
Action
icon of the test case (
Figure 6.1
).
![]() | Warning |
|---|---|
|
Only test cases with the states Draft , Approved and Skip can be executed. |
A detailed
information screen about the test case will be shown
(
Figure 6.2
). Press the
icon on the right side of the screen, for more details about the test case.
Before a test run can be started, the test environment the test is run in and the SUT itself has to be defined.
![]() | Creating Test Environments and Systems under Test |
|---|---|
|
For information on how to create a test environment or a system under test, please refer to Chapter 5, Define . |
![]() | Executing prior revisions of a test |
|---|---|
|
To execute an older revision, choose the revision from the drop down box and press the button. |
Press the button to run the test case. Klaros-Testmanagement will show the following screen ( Figure 6.3 ).
The screen shows the test case overview and the attachments of the test case.
The
attachments can be downloaded by clicking on the
icon.
To begin the manual test run the button must be pressed.
The screen shows the Precondition , Action and Expected values of the test case. Depending on the values the user can choose and press the following buttons:
The test has finished successfully
An error occurred during test execution
A failure of the system under test was detected during test execution
The current step can be skipped without changing the result of the test
Go back to the last step to repeat it again
![]() | What is the difference between a failure and an error? |
|---|---|
|
A failure is a discrepancy between a computed, observed, or measured value or condition and the true, specified, or theoretically correct value or condition. An error is the inability of the system to perform the test correctly. |
The same process has to be applied for each step of the test case.
For each error or failure, or at end of the test execution, Klaros-Testmanagement will show the following screen ( Figure 6.5 ).
![]() | Tip |
|---|---|
|
The description and summary are common for all the steps. |
Press the button to continue the test even if an error or failure occurred, or press the button to finish the test execution .
By clicking on the button, Klaros-Testmanagement will show the test run result of the test case ( Figure 6.6 ).
![]() | Note |
|---|---|
|
If
there are any issue management systems configured for this project, the
will be
enabled. For
details about creating an
issue with Klaros-Testmanagement
see
Section 6.4, “
|
Executing a test suite means running a defined set of tests on a specific version of the SUT in a selected test environment.
The Run a Test Suite page shows all test suites of a project in a list. To get a better overview about the available test suites the sorting and searching functionality of the Filter / Sort panel can be used.
It is possible to search for test suites 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 suites. |
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 suites 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 run test suite page are two fields that can be filtered: ID and Description.
The Type column denotes the operator that is used for the criterion. In the run test plan 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 suites 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 is sorted for. The fields that can be sorted for in the run test suite screen are ID and Description.
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.
To execute a test suite click on the
Action
icon of the test suite in
Figure 6.7
.
![]() | Warning |
|---|---|
|
Test cases with the state Locked or without any steps will be skipped when executing the test suite.. |
A detailed
information screen about each test suite will be shown in
(
Figure 6.8
). Press the
icon, on the right side of the screen, for more details about the test suite.
Before a test run is started, a test environment and a SUT must be chosen.
Before a test run is started, for each test case of the test suite the same actions
described in
Section 6.1.1, “
Run Single Test Case
”
can be applied to execute a test suite.
![]() | Tip |
|---|---|
|
To execute an older revision, choose the revision from the drop down box and press the button. |
By clicking on the button, Klaros-Testmanagement will show the test result of each test case that has been executed in the test suite ( Figure 6.9 ).
![]() | Note |
|---|---|
|
If
there are any issue management systems configured for this project, the
will be
enabled. For
details about creating an
issue with Klaros-Testmanagement
see
Section 6.4, “
|