Please note: This schedule is for OpenStack Active Technical Contributors participating in the Icehouse Design Summit sessions in Hong Kong. These are working sessions to determine the roadmap of the Icehouse release and make decisions across the project. To see the full OpenStack Summit schedule, including presentations, panels and workshops, go to http://openstacksummitnovember2013.sched.org.
During H3 I added some unit tests for tempest. The only tests there right now are very basic and just verify that the wrapper scripts that are used in tox return the correct exit code on success or failure (which was prompted by a bug in one script that super-fixed the gate for a few hours, ie every test always passed)
In the icehouse cycle it would good to start seeing unit tests being added for tempest so that we can verify that tempest works correctly. So, I think it'll be good to have a discussion on which parts of tempest require unit testing and how we should go about implementing them. In addition to anything else related to verifying that tempest itself works as expected and that we don't introduce any regressions through changes to the tempest code.
