Whether you want to build the software, run it, grow the community or just learn more about it, there will be content, workshops and design sessions for you to attend at the OpenStack Summit, Oct 15-18 in San Diego. Stick around Friday for the first OpenStack service day, a 1/2 day beach cleanup.
Currently we make heavy use of nose to do our test running, both in tempest and in the projects, but nose is invasive and when it has issues itself it'll toss away results about the work it's done. There are a bunch of different ways to deal with that ... but the one I'd like to propose and chat about is that we refactor our unittests to be 100% compatible with the standard python unittest framework, augmented by the testtools library (which does many of the things that we've done in openstack in some of our custom base classes and helper functions already) At that point, we can start using other test runners, like testrepository. which allow us to do things more easily, such as only running tests which failed the last time we ran the test suite (useful for a dev cycle focused on fixing a bug) We can also begin to implement parallel testing in tempest.
Simple docs on testrepository parallel runs can be found here: