Story
As a galasa testcase developer I want to use the galasa CLI to create a new project of an example manager, and an extra test class which uses that manager, and an entry in the OBR which refers to that manager
Background
This would be a good feature to then go on and talk about the manager in the docs.
galasactl project create --manager ... would create a manager.
The manager name could optionally be gathered from the CLI syntax. For example with a --managerName xxx parameter. Then we can use that to name the project folder, and manager annotation...etc.
We already have the --package <java-package> parameter for the base package, and bundle.
We should create the new bundle with the manager inside called xxx.manager
What does the manager code actually do ?
- Create an annotation, which can inject a custom object into the testcase.
- Support the cleanup and other lifecycle methods.
I suggest we look at the docker manager for the best example we have. Some of our existing managers are not written anywhere near that.
Tasks
Story
As a galasa testcase developer I want to use the galasa CLI to create a new project of an example manager, and an extra test class which uses that manager, and an entry in the OBR which refers to that manager
Background
This would be a good feature to then go on and talk about the manager in the docs.
galasactl project create --manager ...would create a manager.The manager name could optionally be gathered from the CLI syntax. For example with a
--managerName xxxparameter. Then we can use that to name the project folder, and manager annotation...etc.We already have the
--package <java-package>parameter for the base package, and bundle.We should create the new bundle with the manager inside called
xxx.managerWhat does the manager code actually do ?
I suggest we look at the docker manager for the best example we have. Some of our existing managers are not written anywhere near that.
Tasks