|
Clicking the Settings  icon brings up the "Web Benchmark settings" dialog.
Pressing the OK button accepts any changes you make in this dialog, and stores these in browser history if applicable.
Pressing the Reset button resets everything to Web Benchmark default settings, which contain the settings made on the Web Benchmark control in Web Designer as well.
Pressing the Cancel button discards any changes you make in this dialog.
|
Setting
|
Explanation
|
Display overview of all runs
|
Show in the profile overview the amount of time each action execution has taken The default value is Yes.
This setting is equivalent to the Web Benchmark control property "Display Overview" and allows you to change the value of this property at runtime.
|
Display run times per individual action/event
|
Show in the profile overview the amount of time each action execution has taken. The default value is Yes.
This setting is equivalent to the Web Benchmark control property "Display individual run times on overview" and allows you to change the value of this property at runtime.
|
Display events profile
|
Show the event execution profiles and events per user action in the profiler test details overview. The default value is Yes.
This setting is equivalent to the Web Benchmark control property "Display events profile" and allows you to change the value of this property at runtime.
|
Display message log
|
Allows the user to show or hide the ‘Message log’ tab in the ‘Test run’ dialog. The default value is No, which means that the tab is hidden.
|
Default # of times to run
|
The suggested default number of times that a test is executed when Run profiler  is clicked. The default is 3.
This setting is equivalent to the Web Benchmark control property "Default number of times to profile" and allows you to change the value of this default at runtime.
This setting is a default. You can override it for each individual test before that test is started.
|
Show notification area during batch run
|
When running one or more tests in Profiler mode, a notification area is shown on the right side of the application, showing the progress of the test run and its results so far. It also contains buttons to allow pausing the test, skipping a test, or stopping the run completely. By default, this option is set to Yes, which means the notification area is displayed during profiler runs.
|
Display debug messages in browser console
|
When running tests, this option shows an execution log in the browser control, which shows the current test and action being executed. The log could also be exported to a file if the browser permits this.
|
|
These settings concern behavior of Web Benchmark during recording of a test. These settings can all be influenced too by equivalent properties on the Web Benchmark control that can be changed in the Web Designer.
Setting
|
Explanation
|
Automatically check the value for clicked fields
|
If this setting is set to Yes, the value of an input control in an assert action is recorded as a test action when you click on that control. This allows click-based value validation during a test.
The click itself is recorded too. If you do not want these clicks to be recorded, you can manually remove them from your test definition afterwards.
This setting is equivalent to the Web Benchmark control property "Check the value for selected fields" and allows you to change the value of this property at runtime.
|
Check total number of records and range
|
If this setting is set to Yes, the current record range and the total number of records for a data source is recorded as a test action when that data source is queried or its data set is changed (eg., with the DataSetNumbersControl).
If the control contains click events that have been defined in the Web Designer, these would fire too, and thus the click is recorded in this case as well.
This setting is equivalent to the Web Benchmark control property "Check total number of records and range" and allows you to change the value of this property at runtime.
|
Check number of items in dropdown selects
|
If this setting is set to Yes, the number of child items (option elements) in an InputControl of type 'select' is recorded as a test action when you click on that control.
If the control contains click events that have been defined in the Web Designer, these would fire too, and thus the click is recorded in this case as well.
This setting is equivalent to the Web Benchmark control property "Check number of items in dropdown selects" and allows you to change the value of this property at runtime.
|
|
Setting
|
Explanation
|
Test playback speed (delay)
|
With this setting you can change the delays between actions on a test. Although lower delays give higher speed and are thus best suited for test automation, using a higher delay allows test execution at a more watchable speed, so that you can observe the behaviour of the application better. There are several fixed values for this setting, of which ‘Very fast’ (20 ms delays) is the default. There is also a faster (5 ms) setting, but it has been found to cause tests to fail more easily on older (slower) machines.
|
Max idle time per action
|
This setting allows you to change the maximum amount of idle time that an action may have, i.e. the time it does ‘nothing’ when it is finished. This is different from the ‘playback speed’ in the sense that waiting for a message, displaying and hiding dialogs also are included in this idle time. Higher idle times slow down tests considerably, so a lower value is recommended. The default is 200 ms, but any value between 20 and 5000 is acceptable. A higher value than 5000 is not recommended.
|
Quiet execution (no report)
|
Executes a test without displaying a report when finished. By default, this option is turned off.
|
|
Setting
|
Explanation
|
Automatically save tests in browser storage
|
This setting allows you to save newly created tests in the browser storage immediately when the save dialog is completed. This allows you to save your tests between browser sessions, because the next time you open the application the tests are available again, either immediately (if the ‘Automatically load definitions from browser storage` property of the Web Benchmark control is set to Yes), or by using the ‘Import from browser storage’ button on the ‘Manage tests’ dialog.
Keep in mind that storage space is very limited, about ~400 tests of average size can be stored simultaneously.
This setting is set to No by default.
|
Automatically save test runs in browser storage
|
This setting allows you to save the results of performance tests in the browser storage immediately when the test run completes. This allows you to save your test results between browser sessions, because the next time you open the application these results are available again, either immediately (if the ‘Automatically load definitions from browser storage` property of the Web Benchmark control is set to ‘Yes’), or by using the ‘Import from browser storage’ button on the ‘Manage tests’ dialog.
Test runs take up a lot of space (much more than the definition of a test itself) so use this setting sparingly, or only for small test sets. In the case of large test result sets, exporting from the ‘Profiler overview’ dialog is recommended.
This setting is set to No by default.
|
Default file name for export
|
This setting allows you to change the prefix text used in the file name of exported files. Its default value is ‘TestSuite’, but any name is allowed as long as it contains only characters that are allowed in file names.
|
|
See also
Web Benchmark control properties
The Web Benchmark control
|
