Story
As a Galasa user, I don't want there to be lots of managers released in maven central that aren't implemented, so that I don't want time trying to create Galasa tests with them when they won't provide any real value.
As a Galasa developer, I don't want to keep useless manager bundles in the source code, so there is less to maintain and we don't waste effort building bundles that do nothing.
Background
We need to go through all managers that are in the managers module and delete if they fit into one of these categories:
- Unimplemented (just empty interfaces and classes, todo comments, etc)
- Reference an internal tool
- Outdated (the tool they test is end of life for example and unlikely that any user is going to want to use this manager)
Some managers may be obvious, others may need a closer look to see if they should be deleted, ie, if they look like they have lots of code but it may be bad quality and if there is no IVT or unit tests, no way to know if it works. If possible we may need to attempt to test these managers to see if they work and do anything useful.
Tasks
Story
As a Galasa user, I don't want there to be lots of managers released in maven central that aren't implemented, so that I don't want time trying to create Galasa tests with them when they won't provide any real value.
As a Galasa developer, I don't want to keep useless manager bundles in the source code, so there is less to maintain and we don't waste effort building bundles that do nothing.
Background
We need to go through all managers that are in the managers module and delete if they fit into one of these categories:
Some managers may be obvious, others may need a closer look to see if they should be deleted, ie, if they look like they have lots of code but it may be bad quality and if there is no IVT or unit tests, no way to know if it works. If possible we may need to attempt to test these managers to see if they work and do anything useful.
Tasks