Introduction
The OpenTAP Runner allows for remote starting and control of OpenTAP sessions via NATS. These sessions can create, load, and execute test plans, modify test plan and test step properties, adjust OpenTAP settings, and provide logs and results.
When to use the OpenTAP Runner?
You should consider the OpenTAP Runner if:
- Your solution requires remote interactions with Test Automation
- Your solution is implemented in another language than C#
- You want to integrate with KS8500
Concepts
OpenTAP Runner Communication
The OpenTAP Runner communicates using NATS.io, a high-performance messaging system that provides a simple yet powerful API for building distributed systems and applications.
The NATS Server can be an instance that you control, or you can install the NATS Server TapPackage to let OpenTAP Runner start the NATS Server, which is the recommended approach.
To install the NATS Server package, use the following command: tap package install "NATS Server"
After installation, the runner can be started with the command: tap runner start
The Runner can start Runner Sessions. A Runner Session is a process that also communicates on NATS and exposes the APIs to conduct the same functionality as KS8400A PathWave Test Automation. This includes creating, loading, modifying, and executing test plans.
There are two ways to start a Runner Session through the Runner: using an Image or just a simple copy of the Runner installation. An Image is a set of OpenTAP Packages and a set of OpenTAP Repositories from where to fetch the packages.
The simple case where we ask the Runner to start a Runner Session not based on an Image looks like this:
The more remote-friendly and flexible solution is to use Images. If you require a Session with a different set of packages than the current Runner installation provides, create an Image in the Runner and then use that Image to start a Runner Session:
