51c0f9a353
In many scenario tests, resource either same or different services are created serially which is ok at some extend as most of the resource creation is async operation. But when we wait for resource status serially for example volume to reach to 'avaiable' state, server to become 'SSHABLE' then it add a lot of time in test execution. This commit try to make resources creation and their status waiting in parallel operation so that while we wait for volume to be reach in 'available' state we create server and same time we wait for server to be ACTIVE or SSHABLE. Related-Bug: #2004780 Change-Id: I30f2a44d94dc1e94aefeefecd4dc4e25bdda7a72
Team and repository tags
Tempest - The OpenStack Integration Test Suite
This is a set of integration tests to be run against a live OpenStack cluster. Tempest has batteries of tests for OpenStack API validation, scenarios, and other specific tests useful in validating an OpenStack deployment.
- Documentation: https://docs.openstack.org/tempest/latest/
- Features: https://specs.openstack.org/openstack/qa-specs/#tempest
- Bugs: https://bugs.launchpad.net/tempest/
- Release Notes: https://docs.openstack.org/releasenotes/tempest
Get in touch via email. Use [tempest] in your subject.