Test Run Settings

(Last update of this topic: 05-22-2015)

Navigation:  Settings >

Test Run Settings

(Last update of this topic: 05-22-2015)

Previous pageReturn to chapter overviewNext page

With ersion 5, test runs were integrated into the environment for the first time.

 

As of version 5.2, it is now possible to make adjustments to this test runs.

 

These settings can be accessed via the setup menu (see figure Availability of the settings) (or F8).

 

sp_center_101

Figure 73: Availability of the settings

 

Dependent on your licensing, a certain number of test runs are available which can be freely sorted and shown/hidden.

 

In order to rearrange test runs or complete groups, please use the Drag & Drop function (see figures Move by drag & drop). Groups and test runs can be shown or hidden by means of the respective check boxes.

 

sp_center_102sp_center_101

Figure 74: Move by drag & drop

 

Below the test runs, you will find settings which might be extended to several test runs and partly have effect to the whole environment (see figure General settings).

 

sp_center_104

Figure 75: General settings

 

1.Maximum number of hits in tooltip: Defines the maximum number of error sources displayed in the tooltip of a failed test run.

 

2.Print server: Minimum runtime of the print spooler in seconds -> See Warming Up Time of Print Spooler

 

3.Database server: Free RAM in kb (warning) -> defines the value as of which the test run for identifying the state of the database is declared as a warning due to low working memory.

 

4.Database server: Free RAM in kb (error) -> defines the value as of which the test run for identifying the state of the database is declare as an error due to low working memory.

 

5.Database server: Response time in ms (warning) -> defines the value as of which the test run for identifying the state of the database is declared as a warning due to an inadequate reaction time.

 

6.Database server: Response time in ms (error) -> defines the value as of which the test run for identifying the state of the database is declared as an error due to an inadequate response time.