Integration tests support code is included into production codebase while it shouldn't

[Timur Sufiev]

To make it possible for integration tests to navigate freely through Horizon pages, tables and forms an additional code is included into Horizon - JS files (see https://github.com/openstack/horizon/blob/master/horizon/static/horizon/js/horizon.selenium.js), some additional CSS classes etc.

These things do not affect User-centric Horizon, yet they add a small overhead to a production Horizon codebase. It would be nice to have a way of excluding all these assets using one switch.

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/287793
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=408e358f791956e1c39e4ec2c254926ee48a8014
Submitter: Jenkins
Branch: master

commit 408e358f791956e1c39e4ec2c254926ee48a8014
Author: Timur Sufiev <email address hidden>
Date: Thu Mar 3 16:27:10 2016 +0300

    Move out integration tests scaffolds from Horizon production code

    The main idea of this change is to not include into Horizon production
    code little helper features we need Horizon to have in gating so
    Selenium integration tests could easily navigate through it.

    Closes-Bug: #1560467
    Change-Id: Ib0c973932260ddfe7f1d2cf9fdab7bbbfe298bea

[Davanum Srinivas (DIMS) (dims-v)]

This issue was fixed in the openstack/horizon 10.0.0.0b1 development milestone.