10.4. System

10.4. System
	Chapter 10. Configure

10.4.1. Miscellaneous

Figure 10.11. The “Miscellaneous” Tab

The following settings can be made here to define the behavior of the application:

	Session Timeout
	A changed session timeout does not affect the current session.

Application URL	If the application should be accessed via a proxy server, the configured URL must be specified here. For detailed information on configuring a proxy, see https://httpd.apache.org/docs/2.4/mod/mod_proxy.html (Apache), https://docs.nginx.com/nginx/admin-guide/web-server/reverse-proxy/ (NGinx) https://docs.microsoft.com/en-us/iis/extensions/configuring-application-request-routing-arr/creating-a-forward-proxy-using-application-request-routing (IIS). Clicking the will verify the specified connection. .
Maximum Upload File Size [Byte]	The maximum size for attachments to be uploaded.
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.
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 enabled, users in the Tester and Guest roles will only see their own user entry. Entries from other users will not be displayed.
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.
Only show approved report templates in the evaluate section	If enabled, only reports with the status Approved will be displayed in the Configurable Reports table on the Evaluate / Reports page.
Hide predefined reports	If enabled, the display of the Reports table is suppressed on the Evaluate / Reports page.
Search index	If problems should occur with the general search, a re-indexing of the database can be started here using the Rebuild button.

10.4.2. Notifications

10.4.2.1. Overview Page

For various events, such as the creation of a user account or the assignment of a task, notifications are sent by the system via e-mail. In the Notifications tab, the corresponding conditions are set.

Multiple notification settings can be defined in a notification scheme and reused for multiple projects. When a notification scheme is declared as the default notification scheme, it is automatically assigned to each existing project unless another scheme has already been defined for that project.

	Email-Configuration Required!
	For notifications to work properly, you must configure email server settings as described in Section 10.5.3, “E-Mail” and ensure that all user accounts have a valid email address.

10.4.2.1. Overview Page

The overview page displays all existing notification schemes in a table. New notification schemes are created here.

Figure 10.12. The “Notification Schemes” Page

The table shows the following values:

ID	Assigned automatically.
Name	The name of the notification scheme.
Description	The description of the notification scheme.
Default	When enabled, the notification scheme is the default scheme. If a notification scheme is declared as the default scheme, it is automatically assigned to any existing project, unless another scheme has already been defined for that project.
Events	The number of notification events.
Projects	The number of projects to which this notification scheme is assigned.
Actions	The executable actions.

10.4.2.1.1. Actions

The action column is located on the far right of the table. The following actions can be performed here:

Edit
Duplicate
Delete

10.4.2.1.2. Table Operations

The following operations can be performed in the line above the table on the right:

Filter / Sort
Export
Column selection

All operations are described in detail in Section 5.2.3.1, “Overview Page”.

10.4.2.1.3. Details Page

Figure 10.13 shows the edit options for a notification scheme.

Figure 10.13. The “Add notification” Dialog

This page lists all notifications for the notification scheme. To create a notification, events from a predefined set of available notification events can be individually assigned to one or more recipients (user accounts).

The available notification events are:

Job Assigned	This event is triggered once a Job is saved with a new assignee.
Job ready for execution	This event is triggered whenever a non-executable job becomes executable, or all dependencies of the job are fulfilled (See Section 7.1.2.5, “Dependencies”).
Account Created	This event is triggered once a user account has been created.
Account Password Changed	This event is triggered once an account password has been changed in the local user database.
Test execution failed	This event is triggered after completing a test case execution if a test case step was marked as failed or error during execution.

The available notification targets are:

Assignee	The assignee of the job/test case or the created/edited user account.
Creator	The user responsible for triggering the notification event, e.g. by assigning a job.
Current User	The user currently active.
Specific User	A specific user.

By clicking the Assign projects button, the notification scheme can be assigned to one or more projects (see Figure 10.14).

Figure 10.14. Assigning Projects to a Notification Scheme

10.4.3. Test Execution

10.4.3.1. Explanatory templates for skipped test results

Figure 10.15. The “Test Execution” Tab

In this view, the following settings regarding test execution can be made:

Automatically create new test cases for unknown tests when importing test case results	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.
Create additional test suite results and a corresponding test suite if necessary when importing test case results	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. In addition, a corresponding test-suite is created for the test-suite result, if it doesn't already exist.
Testers may only execute tests via related jobs	If selected, users in the role of Tester may only start tests by executing a job.
Testers may only resume their own test runs	If enabled, users in the Tester role can only resume test runs, that they have started themselves. If a test run was started via a job, they can only resume the test run only if the job is assigned to them.

10.4.3.1. Explanatory templates for skipped test results

If testers want to skip a test case during manual test execution, the system asks for a justification for this. This table contains the templates for these reasons (see Section 8.3.3.1.1, “Skip Test Cases Permanently”). These templates can be applied when skipping.

10.4.3.1.1. Actions

The following actions can be performed in the action column:

Edit
Delete

Figure 10.16. The “Edit Reason” Dialog

10.4.4. Interface

The Interface tab defines the behavior of the user interface.

Figure 10.17. The “Interface” Tab

The following settings can be configured here:

Test Runner starts in tabular view	If enabled, the test runner will per default show the tabular view.
If enabled, show test case information during test execution	If enabled, the test case detail information panel is always expanded per default when launching or executing tests.
Test step editing starts in the tabbed view mode	If enabled, the default view in the Steps tab in the Test Case Details page will be the tabular view.
Rows per table page	This option presets the number of rows per table page.
Maximum preview image height	This option sets the maximum height of the preview images for embedded attachments during test case execution (see Figure 6.45, “An Attachment Reference Replaced by a Preview of the Attachment”).
Maximum preview image width	This option sets the maximum width of the preview images for embedded attachments during test case execution (see Figure 6.45, “An Attachment Reference Replaced by a Preview of the Attachment”).
Show version number in footer	If enabled, the version number of the application is displayed in the footer.
Quote of the day	A message to be displayed on the login screen.
Use random quote of the day	When selected, a random line from the file uploaded below will be displayed as the quote of the day.
Upload Quotes	By clicking the Upload Quotes button, a new text file with quotes can be selected and uploaded. The file must contain one quote per line. The uploaded file can be removed and replaced by the supplied file of the application using the icon . Please refer to Section 4.2, “Quote of the Day” for detailed information on the file format.

10.4.5. Languages

10.4.5.1. Enabling and Disabling Languages

Additional languages can be added to the user interface using language files.

Figure 10.18. The “Languages” Tab

10.4.5.1. Enabling and Disabling Languages

Up to five different languages can be activated at the same time. Clicking the icon adds the selected language, clicking the icon removes it. To add all available languages, click on the or on to remove all languages or use the drag and drop function.

	File Format
	Please refer to Section 4.1, “Languages” for detailed information on the file format.

Klaros-Testmanagement comes with language files in German and English. Support for additional languages can be added by using additional language files if needed. The corresponding language file must be stored in the .klaros/resources/messages directory for this.

Clicking the Refresh messages files button reloads the language files in the .klaros/resources/messages directory while the application is running and displays them in this view.


10.3. Users		10.5. Integration