6.4. Test Environments

6.4.1. Bulk Actions
6.4.2. Creating a Test Environment
6.4.3. Test Environment Details

The Test Environments section allows the management of the test environments in the selected project. Test environments represent the extrinsic settings that may influence the test result. Examples for components of a test environments are the operating system or an application server (e.g. Tomcat 7 on Ubuntu 12.10).

Test environments may be created, removed, updated and assigned to categories on this page ( Figure 6.20). The displayed test environments may be filtered and sorted as described in Section 5.2.5, “Filtering and Sorting”.

The Test Environments Screen

Figure 6.20. The Test Environments Screen


The Test Environments page shows all of the test environments defined for the current project. Clicking on the table fields allows direct editing of the attributes.

The leftmost column allows test environments to be selected for bulk actions. The uppermost checkbox is a global select button, which selects or deselects all elements shown in the table. Please note that the displayed elements are subject to the current search and catagorization criteria.

Test Environments may be viewed on a printer-friendly page as described in Section 5.2.6, “Print Pages” as well as categorized as described in Section 5.2.7, “Categorization”.

Clicking on the delete icon removes the test environment.

[Note] Why is the Delete button sometimes disabled?

Test environments that are referenced by test runs cannot be deleted, so their delete icon is disabled ( ).

Clicking on an edit icon displays the Test Environment Details page of the corresponding test environment.

6.4.1. Bulk Actions

Some bulk actions are available on the Environments page. Bulk actions are described in Section 5.2.10, “Bulk Actions”.

The bulk actions available on this page are: Edit, Print, Delete and Assign to category. The bulk action buttons can be found above the table on the left.

6.4.2. Creating a Test Environment

Clicking on the New button creates a new test environment in the currently selected project ( Figure 6.20). The description field can then be specified. The test environment ID is automatically assigned by Klaros-Testmanagement.

6.4.3. Test Environment Details

This section allows in-depth editing of an individual test environment, including user defined properties. The executed test results and change history for the test environment are also visible in this section.

6.4.3.1. Test Environment Overview

The Test Environment Overview Tab

Figure 6.21. The Test Environment Overview Tab


  • Success

    The success rate shows how many test cases have been successfully executed in this test environment.

  • Progress

    The progress rate shows how many test cases have been executed at least once in this test environment.

    [Note] Note

    In contrast to the success rate, the coverage rate considers only if a test case has been executed at least once in this test environment, regardless of the result (passed, failed, error).

  • Compliance

    The compliance rate shows how many test cases, which are part of this iterations requirements, have been successfully executed in this test environment.

  • Coverage

    The coverage rate shows how many test cases, which are part of a requirement, have been executed at least once in this test environment.

    [Note] Note

    In contrast to the compliance rate, the coverage rate considers only if a test case has been executed at least once in the iteration, regardless of the result (passed, failed, error).

  • Success History

    This graph shows changes in the compliance, coverage, progress and success rates of this test environment over time. The timeline is automatically adjusted depending on the given timeframe.

  • Most unstable Systems under Test

    This table displays the systems under test which have the lowest success and progress rates in conjunction with this test environment.

    [Note] Note

    This table is limited to five entries. The other system under tests can be viewed by pressing the Show All button.

  • Latest failing Test Cases

    This table lists the test cases which recently have been failed during a test run in this test environment alongside with the appertaining test case result.

    [Note] Note

    This table is limited to five entries. The other system under tests can be viewed by pressing the Show All button.

6.4.3.2. User Defined Properties

User defined properties can be used to customize test environments within Klaros-Testmanagement by adding custom fields. This process is described in Section 5.2.12, “User Defined Properties”.

6.4.3.3. Attachments

Attachments may be added to test environments. This process is described in Section 5.2.11, “Attachments”.

6.4.3.4. Results

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

6.4.3.5. Bookmarking Test Environments

Test environments may be linked to from outside of Klaros-Testmanagement using the link on the bookmark icon. Right-click the con and choose Copy Link Location (Firefox/Chrome) or the equivalent option.