Openstack integration testing via tempest is moving towards a plugin framework and we need an efficient mechanism to test these plugin tests hence making sure the new features do not break your working cloud.
Since each project/service will have it's own plugin repository in future we should be able to test API's for each service separately and in an efficient way consuming less time. Hence we will be showcasing a rest based utility where the user only needs to give their plugin name and the cloud credentials as the input and it would in turn run their plugin tests inside the container and once completed it will return test reports along with logs back to the user. These reports can be used to identify any failures in the tests or the added feature itself.
The possible use cases are:
- Easier inclusion of individual component testing into the CI/CD pipeline
- Testing of components can be done on demand even by non-technical resources
This presentation will give an overview about tempest plugin and it's design principles. Attendees can expect to get an understanding into how tempest plugin is created and the key points to remember while creating a new plugin for their project. It will also give insights into the benefits that a tempest plugin has to offer.
Since our tests would be running inside a container we will be giving an overview about docker and how it can be leveraged to run the tempest tests in a fly.
A demo would be given on how to use our rest based utility to run the plugin tests and this would help the attendees to use our utiliy and give feedback as well.