TestArchitect Support

How can we help you today?

Lesson #8: Using an automation harness

Modified on: Wed, 3 Sep, 2014 at 2:57 PM

You may at times find it necessary to do some things in your test that cannot be achieved with built-in actions, nor with the high-level actions that build upon them. Scripted actions allow you to write actions in a third-party programming language, such as Java, Python, or C#.

Such scripted actions can be used to supplement the functionality of built-in TestArchitect actions. Examples of situations that call for scripted actions may include the need to access a specific API, or to perform a complex function like checking the sorting order of a table.

Creating a scripted action

There are two essential tasks involved in creating a scripted action:

Coding the action itself;

Registering the action with TestArchitect, so that TestArchitect knows how to find it and interface with it.