Lesson #8: Using an automation harness

Creating a user-scripted action

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 user-defined actions that build upon them. User-scripted actions allow you to write actions in a third-party programming language, such as Java, Python, or C#.

Such user-scripted actions can be used to supplement the functionality of built-in TestArchitect actions. Examples of situations that call for user-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.

There are two essential tasks involved in creating a user-scripted action:
  1. Coding the action itself;
  2. Registering the action with TestArchitect, so that TestArchitect knows how to find it and interface with it.
Audience: Testers, Automation engineers
What you will learn: