|User Guide / Test execution|
Startup settings are settings which you can configure before launching a test run. These settings are of two types: built-in, and user-defined.
TestArchitect has a number of built-in settings that control how your action lines are handled by the TestArchitect interpreter or automation. (Learn more.) All built-in settings have default values. Those defaults may be overwritten by you prior to the launch of a test run, or during run time from within a test procedure.
User-defined settings are settings that you create at runtime startup, and use within your test procedure in a manner you choose. Your test procedure can read the value of a user-defined setting, store it to a variable, and then use the value of that variable to take appropriate action. Note that, unlike built-in settings, the value of a user-defined setting is not modifiable during runtime.
If you're performing a test run with multiple test modules (as in the case of a test suite or a serial test run), it's important to note that the values of both built-in and user-defined settings are persistent between test module executions. However, the values of built-in settings can be modified by your test procedures, while those of user-defined settings cannot. Hence, note that the built-in setting values in effect upon entry into a test module can depend on that test module's placement in the execution order, whereas that is not a concern for user-defined settings.
Startup settings may be specified in the Execute Test dialog box in TestArchitect Client, or in a test run batch file. When specified in the Execute Test dialog box, the set of settings and their values are retained by TestArchitect and, if not explicitly disabled, apply to all subsequent executions of test runs within the given repository.