User-defined actions

User-defined actions consist of sequences of actions that typically relate to a single business logic function in the application under test.

User-defined actions may be comprised of any type of action: built-in actions, user-scripted actions created with a harness, other user-defined actions, or any combination of the above.

A user-defined action may be called, or invoked, by a test module or other user-defined action. In that sense, it is comparable to what programmers know as a function. It may accept arguments whose values control its behavior, and can also return values through arguments to the calling entity.

For more on user-defined actions, their uses and advantages, see the User Guide.

A user-defined action is created by means of an action definitions which, in the test editor, resembles a test module. In the TestArchitect explorer tree, user-defined actions are organized under the Actions subtree of your project.

Creating a user-defined action is a two-stage process:
Note: Arguments that you create appear at the top of the action definition in the editor, which may lead you to believe that arguments can be created directly in the action definition rather than the New Action dialog box. This is indeed true, but it is strongly advised that you not create arguments this way, as doing so interferes with the process of name change propagation. Similarly, arguments of an existing action should only be added, modified, or deleted through the action's Information tab: