6.2. Iterations

6.2.1. Bulk Actions
6.2.2. Creating an Iteration
6.2.3. Iteration Details

Iterations represent a test cycle in a project. This helps synchronizing the test process with an agile development process (e.g. Scrum). The Iterations page allows management of the iterations in the selected project.

An iteration can be selected for the current project by selecting it in the toolbar on the top of the page (see Figure 6.10, “The Iteration and Project Selection Toolbar”). When an iteration is active, only test objects relevant to the test cycle represented by the iteration are visible. All test runs executed while an iteration is active are automatically linked to the iteration. This helps to quickly assess the test progress and success rates for a given test cycle.

The Iteration and Project Selection Toolbar

Figure 6.10. The Iteration and Project Selection Toolbar


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

The Iterations Screen

Figure 6.11. The Iterations Screen


The Iterations section shows all of the iterations defined for the current project. Clicking on the table fields allows direct editing of the attributes.

The leftmost column allows iterations 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.

Iterations 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 Iteration.

[Note] Why is the Delete button sometimes disabled?

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

Clicking on an edit icon displays the Iteration Details page of the corresponding iteration.

6.2.1. Bulk Actions

Some bulk actions are available on the Maintain Iterations 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.2.2. Creating an Iteration

Clicking on the New button creates a new iteration in the currently selected project ( Figure 6.11). The Name, Start Date and Due Date fields can then be specified. The iteration ID is automatically assigned by Klaros-Testmanagement.

6.2.3. Iteration Details

6.2.3.1. Iteration Overview

The Iteration Overview Tab

Figure 6.12. The Iteration Overview Tab


  • Start Date

    The point in time when the iteration starts.

  • Due Date

    The point in time when the iteration ends.

  • Execution Time (manual) and Execution Time (automated)

    The overall execution times from manual and automated test executions of the iteration are summed up and shown as "execution time (manual)" and "execution time (automated)".

    [Tip] Tip

    Those values can be used for further investigation. An extremely high manual execution time for example could indicate a high rate of retesting or a need for more automated test cases.

  • Success

    The Iteration Success Rate

    Figure 6.13. The Iteration Success Rate


    All test cases which are included in this iteration contribute to this metric (if none are explicitly registered for this iteration, then all test cases are considered). A success rate of 100% means that the latest test run for every test case has been successful.

    [Note] Note

    Even if a test case has been successfully executed in the past, only the latest result is considered for the success rate.

  • Progress

    The progress rate shows how many test cases which are considered for this iteration have been executed.

    [Note] Note

    In contrast to the success rate, the progress rate considers only if a test case has been executed at least once in the iteration, regardless of the result.

  • Compliance

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

  • Coverage

    The coverage rate shows how many test cases, which are part of this iteration's requirements, have been executed at least once.

    [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).

  • Health Matrix

    The Iteration Health Matrix

    Figure 6.14. The Iteration Health Matrix


    This matrix shows the success and progress rate of this iteration for every combination of test environment and system under test which have been configured for this iteration. Both rates are combined to form a weather icon which shows a sun if both the success and progress rate are at 100 percent and a thundery cloud if both rates are below a ceratin level. Moving the mouse cursor over the weather icon displays the success and progress rate in detail.

    [Note] Note

    There are various gradations inbetween the sun and the thundery cloud which can be used to show the condition of the system under test and test environment in this iteration in finer granularity. This can be configured via the health matrix on the reports dashboard.

6.2.3.2. Iteration Properties

This tab ( Figure 6.15 ) allows the user to view or change the following attributes of the selected iteration:

  • ID

    Assigned automatically.

  • Name

    The editable name of the iteration.

  • Description

    A description of the iteration.

  • Success Criteria

    A description of the conditions which need to be met for this iteration to be complete.

  • Start Date

    The date on which this iteration starts.

  • Due Date

    The date on which this iteration is due to be finished.

The Iteration Details Screen

Figure 6.15. The Iteration Details Screen


6.2.3.2.1. User Defined Properties

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

6.2.3.2.2. Attachments

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

6.2.3.2.3. Test Environments, Systems under Test and Requirements Tabs

These tabs allow linking of other artifacts to the iteration. Simply click the Assign button to open a dialog which allows you to select artifacts to assign to this iteration.

Artifacts may be removed by selecting them and clicking the icon above the table.

The Test Environments tab shows the test environments which have been added to this iteration.

The Systems under Test tab shows the systems under test which have been added to this iteration as well as their Compliance, Coverage, Success and Progress metrics. These are metrics relating to the amount of test cases executed and the latest results of these executions.

Progress and Success show these metrics for all test cases in the project, while Coverage and Compliance show them for test cases which cover requirements in this iteration.

Progress

The percentage of the test cases in the project which have been executed in this iteration.

Success

For the test cases executed in the Progress metric, the percentage which were last executed with the result Passed.

Coverage

The percentage of the test cases which cover requirements which are included in this iteration which have been executed in this iteration.

Compliance

For the test cases executed in the Coverage metric, the percentage which were last executed with the result Passed.

The Requirements tab shows the requirements which have been added to this iteration as well as their Compliance and Coverage metrics. These are metrics relating to the amount of test cases executed against the requirements and the latest results of these executions.

Coverage

The percentage of the test cases which cover the requirement which have been executed in this iteration.

Compliance

For the test cases executed in the Coverage metric, the percentage which were last executed with the result Passed.

6.2.3.2.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 iteration as described in Section 5.2.16, “Related Test Runs and Results”.

6.2.3.2.5. Bookmarking Iterations

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