6.3.
Maintaining Systems Under Test
|
||
|---|---|---|
 | Chapter 6. Define |  |
| 6.3.
Maintaining Systems Under Test
|
||
|---|---|---|
| | Chapter 6. Define | |
The Systems Under Test (SUT) section allows maintenance of the systems that can be tested. A SUT is used to represent a version of a software product that can be tested.
The Maintain Systems Under Test section allows the creation, removal and updating of SUTs, searching through all SUTs in the selected project and the assigning of SUTs to categories ( Figure 6.8 ). All of this can be done through the tabular view or on the details page.
The Maintain Systems Under Test screen shows a table with all of the systems under test defined for the current project. Each row of the table represents a system under test, the columns represent attributes of the system under test. The version of the system under test can be changed by clicking on the text field and editing it directly.
The selection column allows systems under test 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 systems under test that match the current search criteria and, if categorization is enabled, are in the currently selected category.
he bulk actions available on the Maintain Systems Under Test screen are: Delete and Assign to category (Klaros-Testmanagement Enterprise Edition only). The bulk action buttons can be found above the table on the left.
Pressing the button submits the changes and pressing the button discards them.
Clicking on the
Delete
icon removes the SUT from the Klaros-Testmanagement
database.
![[Note]](images/note.png) | button disabled |
|---|---|
|
SUTs
which are already referenced by test runs cannot be deleted, so their
|
Clicking on the
Edit
icon causes the details page of the system under test to be displayed.
Clicking on the button allows the user to create a new SUT ( Figure 6.8). An empty row is added at the beginning of the table. The SUT version can be specified. The SUT ID is automatically assigned by Klaros-Testmanagement. The the SUT is assigned to the currently selected project. Pressing the button confirms the creation of the SUT and pressing the button discards the changes. The user can create and save more than one SUT at a time.
If there are user-defined properties for systems under test configured, they can be edited in this tab. Figure 6.9 )
| Note |
|---|---|
|
This tab is disabled if no user-defined properties for systems under test 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 systems under test 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 systems under test 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 SUTs page are ID and Version , 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 SUTs 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 systems under test 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 SUTs page are ID and Version , 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 systems under test 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 systems under test 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 systems under test . The available categories are represented as a collapsible tree, with the name of each category is shown, along with the number of systems under test it contains. The description of each category is shown as a tooltip when its name is hovered over with the mouse pointer.
| |  | |
6.2.
Test Environments
|  | 6.4.
Test Cases
|
