Chapter 2.  Quick Start Guide

Table of Contents

2.1. Setup
2.1.1. Creating a Project
2.1.2. Creating Test Environments
2.1.3. Creating Systems under Test
2.1.4. Creating Test Cases
2.1.5. Creating Test Suites
2.2. Executing Tests
2.2.1. Executing Single Test Cases
2.2.2. Executing Test Suites
2.3. Results and Reports

This section of the tutorial covers the creation of a project, several test cases and a test suite. In addition, the test cases and the test suite will be executed and as a last step, test reports will be generated from the test results. The example project in this guide involves both hardware and software components. For this example, we will consider a printer as our system under test.

Our printer has both hardware and software components which must be tested, as well as various versions of each to be tested in different environments. A good example here are the printer drivers, which have different versions for Windows and Linux, and must also be tested in different versions of each.

The different sorts of testing that must be done require different teams of testers. For our tutorial we will consider two different teams, the hardware team and the software team. The different teams have different issue management systems to track defects. The hardware team uses JIRA, while the software team uses Mantis.

2.1.  Setup

In order to execute and evaluate test cases, you will have to create the test cases itself and also all related test artifacts (e.g. the test environments in which the test cases will be executed) in Klaros-Test­management. In this chapter we will create all artifacts which are necessary for the execution of a single test case.

2.1.1.  Creating a Project

Projects are the base test artifacts in Klaros-Test­management. All test-related artifacts, e.g. test cases or test results, are associated with a single project. A project must therefore be selected in order to engage in any test-related activities. When you first log in to Klaros-Test­management there will be no projects available so you will have to create one.

  1. Press the New button to create a new project.

    The Projects page

    Figure 2.1.  The Projects page

  2. Enter Printer as the project description.

  3. Press the Save button.

    The newly created project will automatically be selected. You will notice that more options have become available here in the Define section, and that some of the buttons in the topbar are no longer grayed out. For now however, we want to edit the project that we have just created.  Assigning Issue Management Systems

  1. Press the icon to go to the Project Details page.

  2. Press the icon beside each issue management system to add them to the project.

    The Properties tab in the Project page

    Figure 2.2.  The Properties tab in the Project page

  3. Press the Save button.  Creating User-Defined Properties

Now is a good time to create some user defined properties for the project to allow for more accurate searching of elements in the project. The process of creating user defined properties is explained in Section 3.3, “User Defined Properties”.

2.1.2.  Creating Test Environments

The next step in setting up a Klaros-Test­management project is to create some test environments to test in. In Klaros-Test­management, a test environment is a description of the extrinsic settings that may influence the test result. This could be the operating system used with the printer or even the physical environment used for the test.

For this tutorial, we will create two software-related and two hardware-related test environments.

  1. Press the Test Environments link in the sidebar.

  2. Press the New button.

    The Test Environment page

    Figure 2.3.  The Test Environment page

  3. Enter Ubuntu 11.4 in the Description text field.

  4. Press the Save button.

  5. Next, create three more Test Environments with the following values in the Description text field:

    • Windows 7
    • Average Room temperature
    • Maximum Operating Temperature  Assigning Test Environments to Categories

Now is a good time to use the categorization feature at this stage. See Section 3.2, “Categorization”.

2.1.3.  Creating Systems under Test

Next we should create some systems under test. In Klaros-Test­management, systems under test represent the versions of the product or software system to be tested. In our example, these will be various printers.

  1. Press the Systems under Test menu entry in the sidebar.

  2. Press the New button.

    The System under Test page

    Figure 2.4.  The System under Test page

  3. Enter the text Printer Model 1 in the Version field.

  4. Press the Save button.

  5. Repeat the process for three more systems under test:


    • Printer Model 2
    • Printer Model 3
    • Printer Model 4  Assigning User Defined Property Values

Please refer to Section 3.3, “User Defined Properties” how to create user defined properties and create a String property Firmware Version and an enumeration property Printerhead Model with the values Model 1 and Model 2 for systems under test. Then you can set values for them.

  1. Press the icon for Printer Model 1.

  2. Press the User Defined tab.

  3. Enter V23.41.06 in the Firmware Version field.

    The System under Test page

    Figure 2.5.  The System under Test page

  4. Select Model 1 in the Printerhead Model dropdown list.

  5. Press the Save button.

  6. Repeat the process for the other three systems under test:

    Version Firmware Version Printerhead Model
    Printer Model 2 V23.41.07B Model 2
    Printer Model 3 V23.41.07B Model 1
    Printer Model 4 V23.41.05 Model 2

2.1.4.  Creating Test Cases

Now it is time to create some test cases. In Klaros-Test­management, test cases represent individual tests to be carried out. We will create test cases for each of the hardware and software teams. First we will create a few hardware test cases. The first test is a verification that the printer upholds our claims about its minimum pages per minute rate.

  1. Press the Test Cases menu entry in the sidebar.

  2. Press the New button.

    The Test Cases page

    Figure 2.6.  The Test Cases page

  3. Enter Test if the printer prints at least 10 page per minute in the Name field.

  4. Select Manual in the Execution field.

  5. Press the Save button.

  6. Press the edit icon on the newly created test case.

  7. Select the Steps tab.

    The Test Case Step tab in the Test Cases page

    Figure 2.7.  The Test Case Step tab in the Test Cases page

  8. Create the following Steps:


    Expected Result

    Start printing the test document

    Start the timer when the first page lands in the tray

    Stop timer when the last page lands in the tray

    The number of pages printed divided by the amount of minutes taken (rounded down) should be 10 or more

  9. Press the Save button.

  10. Next, create the following test cases (each with one test case step):



    Step Description

    Step Expected Result

    Prints test page


    Print the test page using the OS UI

    Page prints

    Detects empty ink cartridge


    Insert empty ink cartridge

    Printer display shows "Cartridge empty" warning

Now you should have three test cases.

2.1.5.  Creating Test Suites

The final step in preparation for testing with Klaros-Test­management is the creation of test suites. In Klaros-Test­management, test suites represent groups of tests to be carried out in sequence. A test suite contains one or more test cases and can be executed as a unit, which allows test results to be grouped together.

[Note] Note

A test suite can contain the same test case multiple times.

  1. Press the Test Suites link in the sidebar.

  2. Press the New button.

    The Test Suites page

    Figure 2.8.  The Test Suites page

  3. Enter Tutorial Hardware Suite in the Name field.

  4. Press the Save button.

  5. Press the icon.

  6. Press the icon on the Detects empty ink cartridge and the Test if the printer prints at least 10 pages per minute test cases.

    The Test Suite page

    Figure 2.9.  The Test Suite page

  7. Press the Save button

Now our project is set up and we can begin testing!