Test isolation for Horizon base tests is broken

[Gabriel Hurley]

Because of the way the core Horizon object is constructed, stored, and referenced, changes to it, its registered dashboards, and its registered panels all persist across tests. This negates any ability to reliably test critical core functionality.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/3997

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/3997
Committed: http://github.com/openstack/horizon/commit/aed4766cc95df806e2d0ac8053231cfe4687e149
Submitter: Jenkins
Branch: master

commit aed4766cc95df806e2d0ac8053231cfe4687e149
Author: Gabriel Hurley <email address hidden>
Date: Thu Feb 9 22:29:23 2012 -0800

    Full support for dashboard and panel configuration via service catalog.

    There are no longer any dependencies on settings for whether or not
    particular components are made available in the site.

    Implements blueprint toggle-features.

    Also fixes bug 929983, making the Horizon object a proper
    singleton and ensuring test isolation for the base horizon tests.

    Fixes a case where a missing service catalog would cause
    a 500 error. Fixes bug 930833,

    Change-Id: If19762afe75859e63aa7bd5128a6795655df2c90