| Chapter 6. Define | ||
|---|---|---|
 |  |
|
| Chapter 6. Define | ||
|---|---|---|
| | |
|
Table of Contents
Defining a Project
Maintaining a Project
Test Environments
Maintaining Systems Under Test
Test Cases
Test Suites
This section describes how to define the main artifacts of Klaros-Testmanagement: the projects, environments, systems under test, test cases and test suites. These artifacts are managed in the define section of the main menu. For each artifact a menu entry on the left hand side is provided.
Maintaining a Project
The Projects section allows to select and manage the projects in Klaros-Testmanagement. The actions used to manage the projects are create, remove, update and search projects.
When accessing Klaros-Testmanagement for the first time it is necessary to create a project to work with. To create a new project select the menu entry Maintain Projects ( Figure 6.1 ) and follow Section 6.1.1.1, “ Creating a Project ” .
After at least one project has been designed, users may select one from a table. This process is described in the following section.
The main screen after a successful login is the Maintain a Project Screen. It gives the user an overview about the projects stored in the Klaros-Testmanagement database. Each project is listed in a single row.
This page allows to creation, removal and updating of projects, as well as searching through available projects ( Figure 6.1 ).
To continue operating, the user is required to select a project. To do this, they must click on the check box of the desired project. If no projects have been created, the user must create one before proceeding. The process of creating a project is described in the next section.
![[Note]](images/note.png) | Choosing a project with the project quick select drop-down field |
|---|---|
|
The header bar of Klaros-Testmanagement contains a drop-down field labeled Project . With this drop-down field the active project can be switched quickly on any Klaros-Testmanagement page . You will be directed to the top page of your current category (Define / Execute etc.). |
After a project is selected, the disabled functions in the navigation bar are made available.
By clicking on the button the user is able to create a new project ( Figure 6.1). An empty row is added at the beginning of the table. A description can be specified. The Project ID is automatically assigned by Klaros-Testmanagement. Press the button to confirm the creation or the button to discard.
It is possible to search for projects 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 projects 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 projects 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 maintain projects 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 projects 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 projects 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.
When the
Delete
icon is clicked, the project will be removed from the list of selectable
projects.
| Why is the button sometimes disabled? |
|---|---|
|
Projects
that already contain some test cases can no longer be deleted by users, so their
|
When the
Restore
icon is clicked, a previously deleted project is restored to the list of
selectable
projects.
Only an administrator is able to restore a deleted project.
When the
Purge
icon is clicked, a previously deleted project is purged from the database.
Only
an administrator is able to purge a deleted project. This operation can not be
undone.
The project description can be used to give a short overview over the project. Clicking on the description field allows the user to directly change the current value ( Figure 6.1 ). Pressing the button submits the changes that have been made, pressing the button discards the changes and pressing the discards the changes and returns you to the project selection page ( Figure 6.1 ).
The issue management systems
that are used in the project can be edited by pressing
the Edit(
)
icon.
The issue management properties page shows two tables: The upper table contains
the
configured issue management systems that are already used in the project, the
lower
table shows all issue management systems that are configured in Klaros-Testmanagement
and not used by the
project. Pressing an add button (
)
adds the corresponding issue management system
to the project. The issue management
system is removed from the
lower table and added to the upper table. A screen shot of
the page for editing the
assigned issue management systems is shown in
Figure 6.2, “The Project Issue Management System Selection Page”.
On this page it is also possible to edit the description of the project and set the
secured flag. If a project is secured, a user must authenticate at Klaros-Testmanagement
to view bookmarked pages. More information about bookmarking is available at
Section 9.4, “Bookmarking Results”
.
Pressing the button submits the changes that have been made, pressing the button discards the changes and pressing the discards the changes and returns you to the project selection page ( Figure 6.1 ).
For instructions on the configuration of issue management systems see
Section 10.5.4, “
Issue Management
”
.
User-defined properties can be used to customize the Systems Under Test, Test Environments, Test Cases and Test Suites by adding additional fields to them.
Pressing the button allows the addition of a new user-defined property. After adding a new property it is possible to choose the entity and property type. There are four possible entities: Figure 6.3, “The Project User-Defined Properties Page”
System Under Test
Test Environment
Test Case
Test Suite
The three possible types of a user-defined property are:
|
Text |
The property will be a text field limited to 1024 characters |
|
True/False |
The property will be a simple check box |
|
Enumeration |
The property will be a drop down box to select a single entry from a predefined list of values |
After the new property is saved the entity and type can no longer be changed. The name of the property and the list of enumeration values can always be changed.
Pressing the button submits the changes that have been made, pressing the button discards the changes and pressing the discards the changes and returns you to the project selection page ( Figure 6.1 ). New user-defined properties can be used as soon as they have been saved.
The button beside the enumeration name opens the menu to edit the values of this enumeration. Figure 6.4, “Editing the values of an enumeration”
It is possible to copy selected test cases or all test cases from another project to the current one. To select test cases, choose a project from the drop down box. Pressing the button causes all selected test cases to be copied to the current project.
| | |
|
| 5.2. Main Functions |  | 6.2.
Test Environments
|
