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
- Coding the action itself;
- Registering the action with TestArchitect, so that TestArchitect knows how to find it and interface with it.
What you will learn:
- How to invoke a harness action
- How to develop a custom harness action
- Accessing the methods and functions of the ABT library in your code
- Writing harness code to interact with a UI
- Reporting results from a harness action
- Basic understanding of the TestArchitect user interface
- Familiarity with the TestArchitect test editor
- Essential understanding of TestArchitect repositories, projects and tests
- Some familiarity with high level programming language(s), such as, Python, Java and C#.
Audience: Testers, Automation engineers
Duration: 2 hours
Understanding harnessesSome project requirements cannot be addressed strictly by building upon built-in actions.
Invoking a scripted action
What it takes to access a scripted action from your test module.
Working with the Python harness
How to implement TestArchitect actions using the Python programming language.
Working with the Java harness
How to implement TestArchitect actions using the Java programming language.
Working with C# harness
How to implement customized TestArchitect actions using the C# programming language.
Summary: What you have learned
What you learned in this lesson: