What it takes to access a user-scripted action from your test module.
From the perspective of a TestArchitect test module, a
user-scripted action looks like any other action: the action line consists of the action name, followed by zero or more arguments. Hence, when
writing an action line that calls a user-scripted action, one only has to know the name of the
action and the arguments it expects.
Note: Unlike the case with built-in actions and user-defined actions, the test editor is not
automatically aware of the existence of user-scripted actions. This means that, by default,
user-scripted actions do not appear in the drop-down list for actions.
If the action is entered correctly, and the build is set up properly,
has no problem with calls to user-scripted actions during compilation and execution. When you enter such action lines that call
actions, they appear in red text (indicating an unknown action), and argument headers
are not automatically displayed.
Tip: A simple, nonessential way to address
this matter is with a stub action. A stub action is basically a
user-defined action that you create with the same name as your user-scripted action. You
can use the stub action to specify any arguments that the user-scripted action uses.
Other than argument actions, the stub action is empty. Hence the
only function of a stub action is to declare an action name and its arguments, and
make it easier for test writers to do their work.