Jump to: navigation, search

Blueprint-speed-up-tempest

Revision as of 21:33, 19 May 2013 by Afazekas (talk | contribs)
  • Launchpad Entry: TempestSpec:speed-up-tempest
  • Created: 18 May 2013
  • Contributors:

Summary

Scale test cases horizontally and vertically.

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

1. 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. 2. fix numbered, order dependent issues 3. Add an option to old and new code path 4. Replace the cheaper setUpClasses 5. Replace the expensive expensive ones (server) 6. 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 might be necessary for testing heat properly, but it will be rare case.

Migration

Change the tox settings. Add post processing

Test/Demo Plan

Unresolved issues


BoF agenda and discussion