Whether you are looking to have to install OpenTAP for the first time or putting the finishing touches on a plugin, the documentation provides details on all the questions you may have about getting setup, the OpenTAP architecture, building plugins, and ultimately running tests.
If you are looking for more specifics take a look at our YouTube channel that walks through various aspects of OpenTAP. We have many examples as well to show different features of the SDK. Still can't find what you are looking for? Ask about it on our forum.
Packages and plugins
The greatest power of OpenTAP lies in its extensible plugin architecture.
A plugin provides a particular function, a set of related functions, or a diverse library of functions. For example, a plugin could provide a new test step, or a new result listener. Plugins come in packages – a versioned collection of plugins. Plugins vary widely in the functionality they provide.
All essential plugins to get started, including a Demonstration package, are available in the OpenTAP Package Repository. You'll find other advanced plugins, such as REST-API, Python, SSH, and PostgreSQL database, appearing on an ever-growing list.
Using the package manager
Installing, uninstalling, upgrading, downgrading, and managing dependencies are all managed by the OpenTAP Package Manager. A package declares its own dependencies and OS/CPU compatibility. The Package Manager resolves those dependencies with the packages in your current installation, if possible. There is a publicly hosted package repository at packages.opentap.io, but it is also possible to host and manage your own plugins simply on a network shared drive internally.