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.
We mock a lot and end up relying heavily on manual testing to find out when one of the many APIs we depend on has changed in a backwards incompatible way, and other surprises. Horizon would greatly benefit from a wider set of integration tests that also exercises all of our interfaces to other projects.
Suggestions and issues to work through:
* How to write useful, durable tests that won't need to be modified all the time because e.g. a button's location has been adjusted?
* Implementation ideas:
* Separate, self-contained new tests?
* Part of the Django Selenium tests?
* A "mocking" switch that could turn mocking on or off: in e.g. a fully set up devstack environment, run the tests without mocking?
* Other ideas?
* Where should they live: in our tree to be easily modified alongside the main code, in Tempest, elsewhere?
* Tooling: Selenium, PhantomJS, CasperJS, Splinter, other...? Any previous experience to share?
