Parameters in Configuration files (globals
)¶
Generally it’s not needed to change parameters in the config files during manual or automated execution, as the parameters have default values or are anyway defined in the Testrun definition. Still sometimes it’s very handy to change them on the fly, for instance to slowly retest a single testrecord or to not close the browser after an error.
Parameter |
Description |
---|---|
|
As you move your maturing software through the system landscape, you might still need regression test results based
on “old” release functionality, while on lower stages you might want to (regression)-test already newer versions
or newer functionality. In
|
|
When set to |
|
When the browser or script finds an error, it usually takes a screenshot and moves on to the next testcase. With this setting to |
|
Set the value to |
|
Which lines from datafile to process.
Combinations are possible and allowed, in this case separate the numbers by comma e.g. |
|
If the testcase is WEB-Testing, then you can overwrite the browser, which is defined inside the testrun definition. If the testcase is not a Web-Testcase this setting doesn’t have any effect. Valid values are |
|
Number of parallel sessions to be executed. Values depend largely on your hardware and internet connection. Debugging works only in a single session. |
|
Creates a very detailed trace of network activity of the browser(s). In the output file you’ll find another Tab “Network”, that holds all API-Calls from the frontend (including header, payload and answer). |
# Todo: BrowserAttributes