In addition to being modifiable from within your test procedures, built-in settings
can have their values set by you just prior to the launch of your test run.
As with user-defined settings, you may use the Execute Test
dialog box's Startup Settings tab to also create new startup
settings for built-in settings. Note the distinction, however: in the case of a new
built-in startup setting, you are not creating a new built-in setting.
Instead, the purpose of a built-in startup setting is to override TestArchitect's default value for that setting.
That is, the value you set for a built-in startup setting becomes the value of that
setting at the start of execution of each affected test run.
To set a new value for a built-in setting from TestArchitect Client, carry out the following steps:
The new value for the built-in setting takes effect when you click the
button, overriding the setting's default value at
the start of the test run. When the test run ends, built-in settings and their
startup values are displayed in the test result
setting values are persistent across test modules within a test run. That is,
the value of a built-in setting upon entry into a test module will be whatever
its value was upon exit of the preceding test module in the run. Neither startup
setting values nor system default values are restored between test modules.
Hence, be aware of the fact that, when you execute test suites or serial test
runs, the value of a given built-in setting at the entry point of a test module
may depend upon that test module's placement in the execution order.
If you choose to generate a batch file (learn more), the parameter /startupsettings specifies the defined settings
and their values. Multiple settings are separated with semi-colons.