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 protected]> 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 ** Changed in: horizon Status: In Progress => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Dashboard (Horizon). https://bugs.launchpad.net/bugs/1560467 Title: Integration tests support code is included into production codebase while it shouldn't Status in OpenStack Dashboard (Horizon): Fix Released Bug description: 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. To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1560467/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp

