Chapter 6. Define

Table of Contents

6.1. Projects
6.1.1. Creating a Project
6.1.2. Deleting a Project
6.1.3. Restoring a Project
6.1.4. Purging a Project
6.1.5. Editing a Project
6.1.6. Project Details
6.2. Iterations
6.2.1. Bulk Actions
6.2.2. Creating an Iteration
6.2.3. Iteration Details
6.3. Requirements
6.3.1. Remote Requirements Management System Synchronization
6.3.2. Bulk Actions
6.3.3. Creating a Requirement
6.3.4. Requirement Details
6.4. Test Environments
6.4.1. Bulk Actions
6.4.2. Creating a Test Environment
6.4.3. Test Environment Details
6.5. Systems under Test
6.5.1. Bulk Actions
6.5.2. Creating a System under Test
6.5.3. System under Test Details
6.6. Test Cases
6.6.1. Bulk Actions
6.6.2. Creating Test Cases
6.6.3. Test Case Details
6.7. Test Segments
6.7.1. Bulk Actions
6.7.2. Creating Test Segments
6.7.3. Test Segment Details
6.8. Test Suites
6.8.1. Bulk Actions
6.8.2. Create Test Suites
6.8.3. Test Suite Details

In the Define section, Projects, Iterations, Requirements, Test Environments, Systems under Test, Test Segments Test Cases and Test Suites can be created and edited. There is a menu entry on the left-hand side for each of these object types.

6.1. Projects

Projects represent a specific test project and contain all corresponding objects such as test cases, test runs, test results and much more.

After a successful login the Projects page is shown. It gives the user an overview of the projects stored in the database. Projects may be created, removed and updated on this page ( Figure 6.1). The displayed projects may be filtered and sorted as described in Section 5.3.6, “Filtering and Sorting”.

The “Projects” Page

Figure 6.1. The Projects Page


When accessing Klaros-Test­management for the first time, it is mandatory to create a project to work with. To create a new project, select the menu entry Projects ( Figure 6.1) and follow Section 6.1.1, “Creating a Project”.

If at least one project has been created, users may select one by clicking on the check box of the desired project in the leftmost or rightmost column. This will activate all project dependent pages, like Test Cases or Requirements.

[Note] Choosing a Project with the Project Quick-select Drop-down Field

The header bar contains a drop-down field showing the name of the currently active project. With this drop-down field the active project can be switched quickly. The user will be directed to the top page of your current category (Define / Execute etc.).

6.1.1. Creating a Project

New projects may be created by clicking the New button ( Figure 6.1). A new row is added at the top of the table. The Project ID is automatically assigned by Klaros-Test­management, but the description can be specified.

6.1.2. Deleting a Project

Clicking the icon will lock the project and remove it from the list of selectable projects.

[Note] Why is the Delete icon sometimes disabled?

Projects that already contain some test results can no longer be deleted by managers, so the delete icon is disabled ( ). Only an administrator can delete a locked project. Locked projects may be restored as long as they have not yet been purged from the database.

6.1.3. Restoring a Project

Clicking the icon will unlock a previously locked project. It will be shown in the list of selectable projects again. Only an administrator is able to restore a locked project.

6.1.4. Purging a Project

When the icon is clicked, a previously locked project is purged from the database. Only an administrator is able to purge a locked project. This operation cannot be undone.

6.1.5. Editing a Project

The project description can be used to give a short overview of the project. Clicking on the Description field allows the user to directly change the current value ( Figure 6.1).

6.1.6. Project Details

This page allows in-depth editing of an individual project, including adding/removing issue management systems and user-defined properties. The executed test results and the change history of the project are also visible.

6.1.6.1. Issue Management

The issue management systems that are in use in the project can be edited here.

[Note] Creating Issue Management Systems

Before issue management systems are available on this page, they must first be created by an administrator.

For instructions on the creation of issue management systems, see Section 10.5.1, “Issue Management Settings”.

The integration tab in the project details page shows two tables: The left table contains the issue management systems that are available, while the right table shows the issue management systems that are already assigned to the project. Pressing the icon adds the corresponding issue management system to the project. To add all issue management systems press the icon. The and are used in the same way to unassign issue management systems. Is is also possible to drag and drop an issue management system to a list.

The “Issue Management” Tab

Figure 6.2. The Issue Management Tab


6.1.6.2. Requirements Management

See Section 10.5.2, “Requirements Management Settings” for more information about how to connect remote requirements management systems to Klaros-Test­management.

6.1.6.2.1. Connecting a Requirements Management System
The “Requirements Management” Tab

Figure 6.3. The Requirements Management Tab


A project can be connected to an requirements management system via the the Requirements Management tab on the project details page. This tab will show a dropdown list of all available requirements management systems.

[Important] Important

In order to connect a RMS with a project, the RMS has to be configured in the Configure section first (see Section 10.5.2, “Requirements Management Settings”).

After pressing the Save button, an background synchronization will start that will load all requirements from the configured RMS and stores them in Klaros-Test­management.

[Note] Note

Synchronizing requirements can take up a huge amount of time depending on the number of requirements on the remote side. Klaros-Test­management has a built-in scheduler that will synchronize all requirements of all connected requirements management systems for all enabled projects in Klaros-Test­management in specified intervals.

[Warning] Warning

When switching to a remote RMS, if any local requirements have been created, they will become invisible for all users and will not appear in any report anymore! Switching back to local requirements management will enable those requirements again, though.

Linking Types

After selecting a requirements management system from the dropdown list, a list of types appears. As per default, all types are selected, which means that a background synchronization will synchronize requirements of any type.

The Synchronized Types of the Requirements Management System

Figure 6.4. The Synchronized Types of the Requirements Management System


Linking Fields

Administrators and project managers can link individual fields between the remote requirements management system and Klaros-Test­management. When using Jira, as per default, the Description, Priority and Summary fields from the remote RMS (if they are available) are linked to the Description, Priority and Name fields in Klaros-Test­management. In addition to that, the Jira Status field is automatically mapped to a dedicated Status field that is only displayed if RMS synchronization is enabled.

There are three types of fields for both sides, String, Enum and Boolean.

[Note] Note

An enum field in Klaros-Test­management can only be linked to an enum field of the remote RMS, but an enum field of the RMS can be linked to a string or boolean field in Klaros-Test­management.

Linking Enum Values

When linking enum fields of both sides, it is necessary to indicate which enum values should be linked together. Otherwise, all values of the RMS will be mapped to the default enum value of the Klaros-Test­management field.

Clicking the icon of an enum linking opens up a dialog where individual values can be linked.

Linking Enumaration Property Values

Figure 6.5. Linking Enumaration Property Values


[Note] Note

Multiple enum values of a remote enum property can be linked to the same enum value of a property in Klaros-Test­management.

Synchronizing Enum Values

When linking enum fields, it is often tedious to keep the list of selectable values in sync. For this, an automated synchronization mechanism for enumeration values is available using the Auto Sync column.

Using AutoSync requires that the remote property is an enum property. In addition, the local property should be set to a user defined requirement enum property. Once done, the Auto Sync checkmark field will appear in the list.

[Note] Note

It is not necessary to specify all the enum field values for the custom enum property. Once the Auto Sync flag is set, Klaros-Test­management will automatically ask the remote system for available values and create them dynamically for the local enum property, removing existing values if necessary.

6.1.6.2.2. Switching the Assigned Requirements Management System

The requirements management system (RMS) of a project can be changed any time. All currently existing requirements of the project will be disabled, as long as another RMS is used.

6.1.6.3. User Defined Properties

User defined properties are used to customize objects within Klaros-Test­management by adding custom fields. This process is described in Section 5.3.13, “User Defined Properties”.

6.1.6.4. Copying Objects between Projects

It is possible to transfer objects from one project to another. This function can be accessed on the Copy Objects tab. To copy objects, a Source Project has to be selected first. This opens up several tabs with requirements, test environments, systems under test, test segments, test cases and test suites from the source project.

Copying Objects to another Project

Figure 6.6. Copying Objects to another Project


There are two modes available to the copy function.

  • Copy Mode
  • Synchronize Mode

In the Copy Mode, copies of the selected objects are created in the target project. These copies will not have any back-references to their source objects, so changes to the source objects will not be reflected in the target objects (and vice versa).

In the Synchronize Mode, copies of the selected objects are created in the target project. These objects will be linked to their original objects in the source project. The synchronized objects will not be editable in the target project. Changes in the source objects can be synchronized to the copies at any time.

[Tip] Why should I use synchronized objects?

With synchronized objects, you can keep a shared pool of test cases in a reference project, which you can reuse in other projects. These synchronized copied will be read only in the target projects and only editable in the reference project.

When changes are made to the synchronized objects in the source project, an update icon ( ) will be shown. This allows to update the synchronized object with all pending changes, including all of their revisions ()if supported by the object.

[Note] Not all object types are currently supported in synchronize mode

Currently only test cases and test suites are supported for synchronize mode.

Depending on the currently selected copy mode, the content of the displayed tabs will change. Already synchronized objects, that have no pending changes, will not be shown in this list. Click the Show all button to show these too.

After selecting the objects to copy, pressing the Copy button opens up a dialog with a summary of all objects that are going to be transferred to the current project. Pressing the Ok button starts the copy process (see Figure 6.7, “Copying Objects from Another Project”).

Copying Objects from Another Project

Figure 6.7. Copying Objects from Another Project


Checking the Keep test case states checkbox keeps the state of all test cases while copying. Unchecking this checkbox sets all test case states to Draft.

[Note] Note

When copying a test suite, all test cases that are part of this test suite are also being copied.

6.1.6.5. Securing access to the Project

A project can be secured by checking the Disable anonymous project access flag. If this flag is checked, a user must be logged into Klaros-Test­management to view bookmarked pages. More information about bookmarking is available at Section 9.17, “Bookmarking Results”.

6.1.6.5.1. Assigning Project specific Roles
The “Access” Tab

Figure 6.8. The Access Tab


Klaros-Test­management Enterprise Edition integrates a rights and role system with its user management system (see Section 10.3, “Users”). In the Access tab, administrators and test managers can assign and change project roles for individual users. For example, a user with the global role tester can be assigned to one project as a tester and to another project as a test manager.

Initially, every project can be accessed by every user. If at least one tester or test manager has been assigned to a specific project, access to this project is restricted for all other users without an assigned role.

Pressing the Assign button opens up a dialog (see Figure 6.9, “The Access Dialog ”) where new users can be added to the project.

The “Access” Dialog

Figure 6.9. The Access Dialog


[Note] Every project needs at least one test manager

A project needs at least one assigned test manager. When trying to save a project which has no assigned test manager, a warning message will be displayed in the log panel (see Section 5.3.2, “The Log Panel”).

6.1.6.5.2. Results

The results tab is further divided into a Test Runs, Test Case Results and a Test Suite Results tab, showing the test results related to this project as described in Section 5.3.17, “Related Test Runs and Results”.