Difference between revisions of "Blueprint-speed-up-tempest"
| Line 32: | Line 32: | ||
== Implementation == | == Implementation == | ||
| − | + | # Increase the single thread risks in order to be less confuse-able with parallel issues. | |
The tempest code uses waits for delete to mitigate the chance of running out from resources, this type of issue will happen in parallel. | The tempest code uses waits for delete to mitigate the chance of running out from resources, this type of issue will happen in parallel. | ||
| − | + | # fix numbered, order dependent issues | |
| − | + | # traceable logging ?? | |
| − | + | # add an option to old and new code path | |
| − | + | # scale horizontally | |
| − | + | # Add resource scheduler for resource reuse | |
| − | + | # traceable logging ?? | |
=== UI Changes === | === UI Changes === | ||
| Line 54: | Line 54: | ||
10GB volume storage will not be enough, but the Thin provisioning can help. | 10GB volume storage will not be enough, but the Thin provisioning can help. | ||
| − | Probably we will need to use a more than 64 MB memory flavor type might be necessary for testing heat properly | + | Probably we will need to use a more than 64 MB memory flavor type, it might be necessary for testing heat properly. |
=== Migration === | === Migration === | ||
| Line 68: | Line 68: | ||
* https://bugs.launchpad.net/nova/+bug/1016633 | * https://bugs.launchpad.net/nova/+bug/1016633 | ||
| − | + | * admin test can cause issues | |
| + | * whitebox tests usually needs less noise | ||
== BoF agenda and discussion == | == BoF agenda and discussion == | ||
Revision as of 18:36, 23 May 2013
- Launchpad Entry: TempestSpec:speed-up-tempest
- Created: 18 May 2013
- Contributors:
Contents
Summary
Use horizontally and vertically scaleable test runner.
Release Note
Rationale
The gate time has impact to the development speed. Parallel test case execution on multiple machines can dramatically speed up Unit Test execution.
User stories
- 'Gate is tooo slow'
- 'I would like use the same test runner with all OpenStack component and handling the test runs in similar way'
- 'I would like to follow the xUnit recommendations '
Assumptions
Happier developers.
Design
- Replacing the notesttests test runner to testtools/testresources/testrepository combination.
- Mitigate the common fixture usage
- Maintain test capability without admin rights
Implementation
- Increase the single thread risks in order to be less confuse-able with parallel issues.
The tempest code uses waits for delete to mitigate the chance of running out from resources, this type of issue will happen in parallel.
- fix numbered, order dependent issues
- traceable logging ??
- add an option to old and new code path
- scale horizontally
- Add resource scheduler for resource reuse
- traceable logging ??
UI Changes
output will change.
Code Changes
Remove complex skip decisions, test selection should be done by attributes based on the configuration file and skip exceptions.
Additional Notes
The test cases rarely needs to writes to the volumes. 10GB volume storage will not be enough, but the Thin provisioning can help.
Probably we will need to use a more than 64 MB memory flavor type, it might be necessary for testing heat properly.
Migration
Change the tox settings. Add post processing
Test/Demo Plan
Unresolved issues
- https://bugs.launchpad.net/nova/+bug/1016633
- admin test can cause issues
- whitebox tests usually needs less noise
