Unit tests should not be strict on html contents

[Diana Whitten]

Several unit tests are using an expected string value and comparing the entire contents of an HTML element just to determine if it contains a class of 'disabled'.

This makes Horizon extremely difficult to customize and makes the unit tests extremely fragile.

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

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

commit d76a61346ebc0d7eb860fe72230ea3a9d1c88022
Author: Steve McLellan <email address hidden>
Date: Tue Nov 17 12:36:31 2015 -0600

    Make unit testing less reliant on HTML fragments

    Some tests check for equality with quite large HTML fragments, when
    the test is only interested in certain specific things (and not style
    changes etc). This patch alters some of those tests (specifically ones
    that were tripping up a dependent patch, but can be expanded) to check
    the context data of the response, since the actual rendering is tested
    by horizon's tests.

    It also adds tests to check context data in 'normal' circumstances so
    that no test coverage should be lost by this.

    Change-Id: I09be82058edc923521ffb4c022515845a18b158d
    Closes-Bug: #1517084

[Doug Hellmann (doug-hellmann)]

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