Jump to: navigation, search

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

Line 38: Line 38:
 
currently, there will be no operational changes and this can be landed
 
currently, there will be no operational changes and this can be landed
 
in master.
 
in master.
 
=== Security and Internal Server Error Considerations ===
 
  
 
=== Additional Notes ===
 
=== Additional Notes ===

Revision as of 18:56, 18 May 2013

  • Launchpad Entry: TempestSpec:speed-up-tempest
  • Created: 18 May 2013
  • Contributors:

Summary

Ruining test cases in parallel.

Release Note

Rationale

Parallel test case execution on multiple machines can dramatically speed up Unit Test execution.

User stories

'Gate is tooo slow'

Assumptions

Gate jobs will speed up.

Design

Replacing the notesttests test runner to testtools/testresources/testrepository combination.

Implementation

UI Changes

Output will change.

Code Changes

Encapsulate the setUpClass() _contents_ into fixtures and testresources. Then, the body of the setUpClass should only contain calls to instantiate the fixtures. If the tests are run via nosetests as currently, there will be no operational changes and this can be landed in master.

Additional Notes

10GB volume storage will not be enough, but the Thin provisioning can help. The test cases rarely needs to writes to the volumes.

More then 64 MB memory flavor type might be necessary for testing heat properly, but it will be rare case.


Migration

?

Test/Demo Plan

?

Unresolved issues

https://bugs.launchpad.net/nova/+bug/1016633


BoF agenda and discussion