This page manages the settings for the behavior and appearance of Klaros-Testmanagement. It contains five tabs, Miscellaneous, Notifications, Test Execution, Interface and Languages.
This tab contains settings regarding the behavior of Klaros-Testmanagement application. The following settings can be made here:
This URL must only be provided if the application is accessed through a proxy server. The proxy is responsible to redirect the user request to a physical URL. The URL specified in the proxy must be entered here. More information about rewriting URLs can be found at http://httpd.apache.org/docs/2.0/mod/mod_proxy.html.
Press the Check Application URL link to test if the URL has been entered correctly.
Maximum Upload File Size [Byte]
The maximum attachment size which can be uploaded. Changing this value requires a restart of the application server.
Use the default container session timeout
If checked, the default tomcat session timeout will be used (30 minutes).
Session Timeout (Minutes)
If the checkbox above is unchecked, this value is used as the session timeout.
A newly set session timeout will not be applied to currently running sessions.
Only Administrators can create Users
If checked, only administrators can create users. If unchecked, managers can also create users.
Only Managers and Administrators can see other users in the user management
If this option is set, testers and guests will only see their own user entry. Turn on this option if you like to hide user information from the eyes of your testers and guests.
Only managers are allowed to change a job status:
If checked, only users in the role of Manager or higher may change the status of jobs.
Notifications will be sent by the system via email for various events like creating a user account or assigning a job. This section allows to configure the conditions under which these notification emails will be sent.
In a notification scheme, multiple notification settings can be defined and reused across various projects. If a notification scheme is declared as the default notification scheme, it is automatically assigned to every existing project, unless another scheme has already been defined for this project.
Figure 10.11 shows the notification scheme definition tab.
For notifications to work properly it is required to configure the email server settings as described in Section 10.5.3, “E-Mail Settings” and make sure that all user accounts contain a valid email address.
Clicking thebutton creates a notification scheme. The Name and Description fields can be set directly here. If the Default check box is activated this notification scheme becomes the default notification scheme which is applied to every project per default.
By clicking the icon the notification edit tab is shown where the notifications and project assignments can be defined. Clicking the icon causes the notification scheme to be deleted.
When thebutton is clicked the notification scheme will be saved. The discards the changes made.
Figure 10.12 shows the edit options for a notification scheme.
The list shows the notifications already defined for the notification scheme currently edited. For creating a notification, the user may individually assign events from a predefined set of available notification events to one or more notification targets (user accounts).
The available notification events are:
This event is triggered once a Job is saved with a new assignee.
This event is triggered once a user account has been created.
This event is triggered once an account password has been changed in the local user database.
This event is triggered after completion of a test case execution if a test case step was marked as failed or erroneous during execution.
This event is triggered whenever a non-executable job becomes executable, because all dependencies of the job are fulfilled (See Section 184.108.40.206, “Dependencies”).
The available notification targets are:
The assigned user account for a job assignment or the currently created/changed user account.
The user responsible for triggering the notification event, e.g. by assigning a job.
The user currently active.
A specific user.
Using thebutton the user may assign a notification scheme to a set of projects, thus overriding the default notification scheme.
Figure 10.13 shows the dialog for project assignement.
This tab contains settings regarding the test execution. The following settings can be made here:
If selected, a test case is automatically created for the respective test case information in the result file. This information may vary with the import format.
If selected, a test suite result is automatically created for the respective test suite information in the result file. This information may vary with the import format. Additionally a corresponding test suite is created for the test suite result if it did not yet exist.
If selected, users in the role of Tester may only start tests by executing a job.
If selected, users in the role of Tester may only resume test runs they have started themself. If a test run has been started via a job, they can execute it only if the job is assigned to them.
This table (initially empty) contains all defined templates for reasons for skipping test cases during execution. When skipping a test case during manual test execution, testers are asked for a reason for skipping the test case and can choose from those templates in addition to providing their own notes (see Section 8.4, “Permanently Skipping Test Cases”).
Click the icon. Click the icon to remove it.button to create a new reason template, which will add a new entry to the table. To modify a reason template, click the
This tab contains settings regarding the behavior of the user interface in Klaros-Testmanagement.
The following settings can be made here:
If true the testrunner will per default show the tabluar view.
If true, the test case detail information panel is always expanded per default when launching or executing tests.
If true, the default view in the Steps tab in the Test Case Details section will be the tabular view.
With this option, the number of rows per table page can be set.
This option sets the maximum height of the preview images of attachments during test case execution (see Figure 6.34, “An Attachment Reference replaced by a Preview of the Attachment”).
This option sets the maximum width of the preview images of attachments during test case execution (see Figure 6.34, “An Attachment Reference replaced by a Preview of the Attachment”).
The message to display on the login screen.
If true, a line from the file uploaded below will be displayed as the quote of the day.
This allows the user to upload a quotes file to be used for the random quote of the day. This should be a text file named quotes.txt with one quote per line. The details of the current quotes file are shown below, including a download link for the file itself, and a delete button, which causes the default quotes file to be restored.
Please refer to Section 4.2, “Custom Quotes” for detailed information on the file format.
Klaros-Testmanagement supports adding additional languages
Up to 5 languages can be enabled at once. Enabled languages are added to the language selection panel at the top of the screen in Klaros. To enable a language, click the . Click the icon to remove the language from the table. To add all available languages press the . To remove all languages press the . It is also possible to add or remove languages using drag and drop.
Please refer to Section 4.1, “Languages” for detailed information on the file format.