| Chapter 8. Execute | ||
|---|---|---|
 |  |
|
| Chapter 8. Execute | ||
|---|---|---|
| | |
|
Table of Contents
This chapter describes the processes of executing test cases and test suites, continuing interrupted test suite executions and creating 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 of 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 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 run single test case 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 run single test case 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 run single test case 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.
Clicking on the
Action
icon of a test case executes that
(
Figure 8.1
).
![[Warning]](images/warning.png) | 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 8.2
). Clicking the
icon on the right side of the screen displays 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 have to be defined.
![[Tip]](images/tip.png) | 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 6, 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 8.3 ).
This screen shows the test case overview and the attachments of the test case.
Clicking the
icon starts the download of the attachments.
To begin the manual test run, the button must be clicked. By default, the step-by-step instructions screen will open, but this can be changed to the tabular step instructions view by marking the tabular view checkbox.
The step by step instructions screen shows the Precondition , Action and Postcondition values of the current test case step. Depending on the results of the step, the user can click the following buttons:
The test step has been completely successfully
An error occurred during test step execution
A failure of the system under test was detected during test step execution
The current step can be skipped without changing the result of the test
All steps can be skipped without changing the result of the test
Go back to the last step to repeat it again
The same process is applied for each step of the test case.
Clicking the button continues the test even if an error or failure occurred, and clicking the button finishes the test execution .
Clicking the button, causes Klaros-Testmanagement to show the test run result of the test case ( Figure 8.7 ).
The tabular step instructions screen shows the Precondition , Action, Postcondition and Result of all steps, the default result being Unknown .
The following actions can be carried out at any time:
The current step can be skipped without changing the result of the test
Finishes the test run
The test step has been completely successfully
An error occurred during test step execution
A failure of the system under test was detected during test step execution
Clicking on the result of individual steps allows the user to directly set them.
Clicking the button, causes Klaros-Testmanagement to show the test run result of the test case ( Figure 8.7 ).
| 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. |
For each error or failure, Klaros-Testmanagement will show the following screen ( Figure 8.6 ). The button saves the comment and moves on to the next step while the button saves the comment and completes the test case run.
| Tip |
|---|---|
|
The description and summary fields appear in all comment screens. |
The test case results screen allows the user to write a description and summary for the test case run as well as for each individual step in the run. ( Figure 8.7 ).
![[Note]](images/note.png) | Note |
|---|---|
|
If
there are any issue management systems configured for this project, the
button will be
enabled. For
details on creating an
issue with Klaros-Testmanagement,
see
Section 8.4, “
|
Executing a test suite consists of running a defined set of test cases 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 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 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. The fields which can be filtered in the Filter / Sort panel of the run a test suite page are ID and Description , 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 run a test suite 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 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 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 run a test suite page are ID and Description , 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.
Clicking on the
Action
icon of a test suite executes that test suite
(
Figure 8.8
).
| 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
(
Figure 8.9
). Clicking the
icon on the right side of the screen displays details about the test suite.
Before a test run is started, a test environment and a SUT must be chosen.
For each test case of the test suite, the actions
described in
Section 8.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. |
Clicking the button causes Klaros-Testmanagement to show the test result of each test case that has been executed in the test suite ( Figure 8.10 ).
| Note |
|---|---|
|
If
there are any issue management systems configured for this project, the
button will be
enabled. For
details about creating an
issue with Klaros-Testmanagement
see
Section 8.4, “
|
| | |
|
7.4.
Jobs By User
|  | 8.2. Continue Run |
