0.3.0
Added ability to use clouds.yaml with scenario tests
Client tests have been imported from the Sahara repository.
Migrate sahara cli tests from saharaclient to sahara-tests
Yaml-files for deprecated plugins was removed
Tests no longer depend on fake plugin to run
Sahara Tests plugin now uses tempest stable interface
New Features
- User can now use clouds.yaml in the format defined by os-client-config to specify the auth values wanted on a scenario test.
- The tests for the official Python clients have been moved here from the Sahara repository. They are based on the Tempest libraries even they do not follow the Tempest guidelines (as they need to test the Python clients, they do not use the native Tempest clients).
Upgrade Notes
- Migration from novaclient.v2.images to glanceclient
Bug Fixes
- Removed yaml-files for Kilo release
- Removed unused yaml-files for master branch
Other Notes
- Adapt Sahara Tests code to stop relying only on the fake plugin and use the default plugin available. However, it’s worth noting that - if available - the fake plugin will be used.
- Sahara Tests plugin is adapted to use in-tree client, which was migrated from Tempest code. Also, there’s a new stable interface for Service Clients in Tempest, so this change adapts the code to use it.
0.2.0
Discovery of data sources with relative paths is now fixed.
Fix default resource discovery from the installed package.
Migrate auth system from keystoneclient to keystoneauth
Removed the need of a .testr.conf file when calling the test runner.
Bug Fixes
- Datasources with relative paths are now properly found from the default resources.
- The default set of resources (test templates for each plugin, etc) can now be properly discovered when the package is installed.
- A .testr.conf file was previously required in the runner execution directory, now this is handled internally.
Other Notes
- The default timeout for cluster polling was raised from 1800 to 3600 seconds.