Difference between revisions of "Blueprint-speed-up-tempest"

Revision as of 18:37, 23 May 2013

Use horizontally and vertically scaleable test runner.

The gate time has impact to the development speed. Parallel test case execution on multiple machines can dramatically speed up Unit Test execution.

'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 '

Happier developers.

Replacing the notesttests test runner to testtools/testresources/testrepository combination.
Mitigate the common fixture usage
Maintain test capability without admin rights

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.

output will change.

Remove complex skip decisions, test selection should be done by attributes based on the configuration file and skip exceptions.

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.

Change the tox settings. Add post processing

@@ Line 38: / Line 38: @@
 # add an option to old and new code path
 # scale horizontally
-# Add resource scheduler for resource reuse
+# Add test case scheduler which supports resource reuse
 # traceable logging ??