Python objects that conform to the Test Plugin interface and are used to execute a given test. They can be extremely simple or quite complex but, ultimately, they provide a very basic interface to the Orchestrator that’s calling them.
This "interface" would include methods to run(), get_status() [of], and cancel() a plugin. Figuring out how to specify these methods via REST requests is a subject for later...
For now, we need to figure out the most sensible way to structure a Plugin class and any related modules/classes such that the functionality is fairly flexible and extensible.
Brian's proposal describes test plugins as
This "interface" would include methods to
run(),get_status()[of], andcancel()a plugin. Figuring out how to specify these methods via REST requests is a subject for later...For now, we need to figure out the most sensible way to structure a
Pluginclass and any related modules/classes such that the functionality is fairly flexible and extensible.