Startup settings

Startup settings are settings which you can configure before launching a test run. These settings are of two types: built-in, and user-defined.

Built-in settings

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

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.

Warning:

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.

Creating a new user-defined setting
User-defined settings are a useful way of passing information to your test modules prior to startup to get them to behave in a certain way. You can create these settings within TestArchitect Client for either a client-directed test run or to generate a test run batch file.

Creating a startup setting for a built-in setting
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.

Editing an existing startup setting
You can edit the startup attributes of existing user-defined and built-in settings.

Deleting a startup setting
You can delete startup settings of both user-defined and built-in settings.

Related information

get setting

getsetting

GetSetting

Result Details tab

Executing tests from the command line interface


Copyright © 2021 LogiGear Corporation. All rights reserved. LogiGear is a registered trademark, and Action Based Testing and TestArchitect are trademarks of LogiGear Corporation. All other trademarks contained herein are the property of their respective owners.

LogiGear Corporation

1730 S. Amphlett Blvd. Suite 200, San Mateo, CA 94402

Tel: +1(800) 322-0333