Table of Contents
This section describes the plan section of Klaros-Testmanagement. The plan section is used to define and maintain jobs, generate jobs from test cases and test suites, and to track the workload and progress of users in the selected project.
This section is used to define and maintain jobs. Jobs may consist of the execution of test cases or test suites or any other possible task. Jobs can be nested and assigned to individual users. The executions and results of jobs are automatically tracked by Klaros-Testmanagement.
The Maintain Jobs page shows all of the jobs defined for the current project. Clicking on the table fields allows direct editing of the attributes.
The leftmost column allows jobs to be selected and bulk actions to be carried out. The uppermost checkbox is a global select button, which allows bulk actions to be carried out for all jobs that match the current search criteria.
The Action column contains buttons for carrying out actions on individual jobs. The icon opens the Job Details Page for the corresponding job (described in Section 7.1.5, “Job Details”). The icon duplicates the corresponding job, optionally including its sub-jobs. The delete icon removes the corresponding job. The icon executes the corresponding job (described in Section 7.1.4, “Executing a Job”). The icon imports test results if the job references an automated test case.
Jobs may be viewed on a printer-friendly page as described in Section 5.2.7, “Print Pages”.
Some bulk actions are available on the Maintain Jobs page. Bulk actions are described in Section 5.2.11, “Bulk Actions”.
The bulk actions available on this page are: Edit, Delete, Duplicate, Assign to Parent and, if viewing sub-jobs, Move to new Position and Move up one Level. The bulk action buttons can be found above the table on the left.
Clicking the Figure 7.1). The job ID is automatically assigned by Klaros-Testmanagement. The Summary, Priority, Due Date and Assignee fields can be specified here. The new job must be persisted by clicking the Save button.button creates a new job in the selected project (
Jobs can be arranged using the arrow icons in the Arrange column. The icon opens a dialog which allows the user to move the job to a new position, and the and icons change the job hierarchy. Using the icon will put the job in the same hierarchy level as its parent job. Using the opens a dialog which allows the user to choose a new parent job from the job's siblings.
Parent Jobs have specific features:
To subordinate a job, create a job of type Task that does not have a test case or test suite. Then, select a job that should be subordinated by clicking the icon (this job can have a test case or test suite). Here you can choose witch job should be the parent, then click . Next to the job ID the number of subordinate jobs in this parent is shown. The success- and progress rate shown on the parent job is derived from the contained jobs.
Jobs which have a test case or test suite assigned to them may not have sub-jobs, and so will not be available as possible parent jobs in the New Parent Dialog.
Clicking the icon executes the job. A user in the role tester is only able to execute or jobs which are assigned to him.
If the job is associated with a test case, the Run Single Test Case dialog will be opened. A detailed description of how to run a test case can be found in Section 8.2, “Run Test Case”.
If the job is associated with a test suite, the Run Test Suite dialog will be opened. A detailed description of how to run a test suite can be found in Section 8.3, “Run Test Suite”.
If the job is associated with an automated test case, or the test suite contains only automated test cases, Klaros-Testmanagement will display the page to import test results. More information about importing results can be found in Section 8.6, “Import Test Results”.
The job type ( Test Execution - Automated, Test Execution - Manual or Task (if the job isn't related to a test case)).
The status of the job.
The priority of the job.
Who is assigned for this job.
The earliest point in time this job can be executed by a tester.
The point in time where the execution of the job has to be completed at the latest.
Test Case / Test Suite
The test case or test suite which is covered by this job.
System under Test
The system under test which has to be used when executing this job.
The test environment which has to be used when executing this job.
The estimated time needed to complete this job.
The progress rate shows how many test cases which are covered by this job have been executed, regardless the result.
The success rate shows how many of the test cases which are covered by this job have been successfully executed in the latest test run.
Total Time Spent
How much time has actually been spent testing. This value is calculated by adding up the individual execution times from the work log.
The executor which has executed the latest test run of this job.
Latest Test Runs
This graph displays the accumulated test case results of the latest test runs for this job in descending order.
This graph shows the minimum, average and maximum execution times for this job.
Latest Test Runs
This table shows the latest completed test runs for this job.
By default, this table shows only five entries. Pressing the Show all button opens up the results tab in which all test runs are listed.
This section allows in-depth editing of a single job. the executed test results and change history for the Job are also shown in this section. ( Figure 7.4). The Job Properties page allows the user to change the following attributes:
The name or summary of the Job
The description of the Job
The priority of the job. Possible values are, in order of severity, Trivial, Minor, Major, Critical and Blocker. Blocker means that the job should be executed before further progress in the project can be made.
The status of the job. Possible values are New, In Progress, Resolved, Closed, Reopened and Rejected.
The estimated time in hours that the job will take.
The current percentage of completion of the job.
The date when the job should be started.
The deadline when the job should be finished.
The user responsible for the job.
The iteration for the job. A job can only be in one iteration at a time, though it can be moved between iterations.
The test case that should be executed with this job. Either a test case or a test suite can be assigned to a job. This field is unavailable if the job contains sub-jobs.
The test suite that should be executed with this job. Either a test case or a test suite can be assigned to a job. This field is unavailable if the job contains sub-jobs.
System under Test
The system under test for which this job should be executed.
The test environment in which the job should be executed.
It is possible to assign a test case or test suite to a job, but only if the job does not contain sub-jobs. Clicking the icon opens a dialog in which a test case or a test suite can be selected. Only one item can be selected at the same time. Clicking the icon removes the element from the job.
This section also contains a Test Runs tab and a Results tab as described in Section 5.2.17, “Related Test Runs and Results”.
User defined properties can be used to customize jobs within Klaros-Testmanagement by adding custom fields. This process is described in Section 5.2.13, “User Defined Properties”.
Since Klaros-Testmanagement 4.5 it is possible to configure jobs as prerequisites for other jobs. Each job can have any number of required jobs, each with one or more dependency criteria that all need to be fulfilled before the dependent job can be executed. On the Dependencies tab there is an overview of all required and dependent jobs of the currently selected job.
The minimum progress rate of the required job (0-100%).
The minimum success rate of the required job (0-100%).
The latest result of the required job ( Passed, Skipped, Failed or Error). Multiple values can be selected.
The current status of the required job ( New, Reopened, In Progress, Resolved, Closed or Rejected). Multiple values can be selected.
If a job cannot be executed because the dependency criteria of its required jobs are not fulfilled, the icon is displayed instead of the execute icon.
If the dependency criteria of a job is not fulfilled, the job gets marked with the icon.
Attachments may be added to jobs. This process is described in Section 5.2.12, “Attachments”.
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 job as described in Section 5.2.17, “Related Test Runs and Results”.
This tab allows a user to add comments by clicking on thebutton.
The text entered in this dialog will be saved as a comment on the job once the icon, to remove it, click the icon.button is clicked and saved. To modify the comment, use the
Every executed test run related to this job is logged in the Work log tab. It is also possible to add your own work logs to the job. When clicking thebutton a dialog is shown where all the information can be set.
The duration field must contain a number greater than zero in order for the work unit to be logged. Then click icon, to remove it, click the icon.and then , to save your logged work. To modify a work log entry, use the