| Chapter 1. Feature Overview | ||
|---|---|---|
|
 |
|
| Chapter 1. Feature Overview | ||
|---|---|---|
|
|
|
|
Table of Contents
|
Management of Test-related Objects |
All data of a test project like test cases, test suites, test requirements, test environments, test objects/(SuT), test runs and test case results are stored together in a single database. The administration, processing and evaluation of the data is performed via a modern and comfortable web interface. |
|
Agile and Classic Processes |
In addition to classical development processes such as the waterfall or V-Model, iterative and agile methods such as Scrum or Kanban are also supported. |
|
Requirements Coverage |
Test requirements can either be managed directly in Klaros-Testmanagement or synchronized with external sources such as JIRA. The current requirements coverage can be displayed at any time. |
|
Modularization |
Frequently recurring test steps can be combined into segments and can be reused. Test steps can be inserted as in a modular system and maintained with minimal effort. |
|
Sharing |
Test cases and test suites can be centrally maintained and used simultaneously in several projects. Changes are only necessary in a single location and will be propagated to selected projects. |
|
Tracking Changes |
For a seamless tracking of all changes applied to the managed data, such as test cases and test steps, all changes are logged automatically and displayed in a detailed change history. |
|
User-Defined Custom Fields |
Each test project can be configured individually using custom fields. These fields are available for jobs, requirements, iterations, test segments, test cases, test suites, test environments, test systems and test runs. |
|
Categorization, Individual Views |
All involved objects can be categorized and arranged in multiple tree structures as required. This is similar to a file system based on individual criteria and allows different views of a test project. |
|
Saving Binary Attachments |
Additional information such as test data, text documents, graphics, screenshots etc. can be uploaded into the application, saved and assigned to the objects iteration, job, requirement, system under test, test environment, test segment, test case, test step, test suite and test case results. |
|
Import Interfaces for Test Cases |
Existing requirements and test cases can be imported from XML and Excel files. A REST interface, if needed, provides continuous synchronization with an external data source or application. |
|
Revisioning |
Klaros-Testmanagement supports the versioning of test requirements, test segments, test cases and test suites. Each version can be maintained, executed, and evaluated separately. |
|
Task Planning |
At the push of a button, jobs for executing test cases and test suites are created and assigned to individual persons. The status of the job execution is visible at any time. |
|
Test Coordination |
Jobs can be broken down into sub jobs, arranged hierarchically and assigned to testers. By defining dependencies, you can set preconditions for successive test sequences. |
|
Utilization, Progress and Success |
Clear tables and graphs show usage, duration, and progress of each user's test activity. The progress and success rates of the tests are directly available and always up to date. |
|
Test Case Reviews |
Even test cases can be defective. Checking and fixing these tests can be assigned to users as a special job. The further course is logged automatically. |
|
|
|
|
| Klaros-Testmanagement User Manual |  |
Chapter 2. Introduction |