| Chapter 2. Introduction | ||
|---|---|---|
 |  |
|
| Chapter 2. Introduction | ||
|---|---|---|
| | |
|
Table of Contents
Klaros-Testmanagement is an easy to use web based application which helps to organize test projects. Klaros-Testmanagement manages test cases, test suites, information about tested systems and the test environments in which a test have been run. When a test case or plan has been executed its result including the information about the tested system and its test environment, is stored in a database. This enables a full traceability of all test runs. Multiple reports enable an detailed overview of the progress of the test project at any time.
This section gives a short overview of Klaros-Testmanagement. It describes the structure and the relation of the components and features used in the application ( Figure 2.1 ).
The main artifacts of Klaros-Testmanagement are listed below:
Project
A project is the main unit that contains all artifacts that are needed for the test project.
Test Environment
A test environment represents the extrinsic setting that may influence the test result. Examples for parts of an test environment would be the operation system or an application server.
Test System, System Under Test (SUT)
A SUT represents a particular version of the component, system, or product that is tested.
Test Case
The test case is the basic unit of a test process. A test case can be related to many test environments and SUTs thus it is possible to execute the same test cases and get different results.
Test Case Results
After a test case has been executed, it has a result. This result can be Passed, Failed or Error. Klaros-Testmanagement enriches this information with the combination of system under test and test environment for which the test has been run and many other information that can be gathered from the execution, like time of execution of the test.
Test Suite
The test suite is a list of test cases. With test suites, the test cases can be grouped to test suites. A test case can be part of more then one test suite.
Test Suite Results
The test suite result is an aggregation of the result of the test cases that are included in the test suite. The result of a test suite can be Passed, Failed or Error. Additionally the test suite result gets additional information as the system under test, and the test environment in which the plan has been run, its execution time, the person who executed the test suite and much more. The execution of a test suite can be suspended at any time and its execution can be continued later.
There are three Roles for users defined in Klaros-Testmanagement: Administrator, Manager and Tester. These roles are described more detailed in ( Section 2.2, “Roles” ). Figure 2.1 is an overview of Klaros-Testmanagement and displays the user roles and the relation between the artifacts.
After a project has been created, test cases can be added.
Test cases can be grouped to test suites. Before
running the test cases or test
plans, at least one system under test, and at least one test environment has to be defined for
the project.
When all necessary artifacts are defined, a test case can be executed by performing a single test case which will generate a test case result, or a group of tests can be performed by executing a test suite. The outcome of the test case or test suite will be stored in a test case result or a test suite result which contains the individual test case results of that test run.
Besides the test case results and test suite results, Klaros-Testmanagement generates reports that are available to export to five different types of documents (PDF, HTML, CSV, RTF, XML).
![[Important]](images/important.png) | Important |
|---|---|
|
The report generation is not available for all roles. To learn more about the role system see ( Section 2.2, “Roles” ). |
Figure 2.2 shows the structure of a project.
The test case/plan run, test environment and SUT are directly related to a
project, so their existence is essential. To run a
test case/plan it
is mandatory to have a test environment and a SUT configured.
Figure 2.3 shows the relation between test cases and test plans.
Klaros-Testmanagement supports the reuse of test cases. A test case can be part of multiple test suites. The sharing of test cases is only possible inside the same project.
Figure 2.4 shows a workflow for Klaros-Testmanagement and the artifacts created.
As a first step all the objects like test environment and system under test (SUT),
must be defined. Subsequently test cases and test suites can be created.
The statistics of the project are updated for each object added
in Klaros-Testmanagement. The reports can be generated after a test execution.
| | |
|
| 1.2. Klaros-Testmanagement Enterprise Edition Features |  | 2.2. Roles |
