Account for some UI changes in the Chrome Endure docs/plus tests.

Account for some UI changes in the Chrome Endure docs/plus tests.

Change 1: fix a problem where the docs test fails when the UI unexpectedly
and automatically reloads.  The fix is to identify when this happens and
invoke some setup code that allows the test scenario to work properly in
the event that it does happen.

Change 2: modify two xpaths in the plus test to account for UI changes.

BUG=None
TEST=Verified that both tests run for at least several minutes with
these changes.
NOTRY=true


Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=149751

[Nirnimesh, 2012-08-02 23:11:34]

https://chromiumcodereview.appspot.com/10825166/diff/1/chrome/test/functional...
File chrome/test/functional/perf_endure.py (right):

https://chromiumcodereview.appspot.com/10825166/diff/1/chrome/test/functional...
chrome/test/functional/perf_endure.py:978: sort_button.click()
twice?

[dennis_jeffrey, 2012-08-02 23:26:55]

https://chromiumcodereview.appspot.com/10825166/diff/1/chrome/test/functional...
File chrome/test/functional/perf_endure.py (right):

https://chromiumcodereview.appspot.com/10825166/diff/1/chrome/test/functional...
chrome/test/functional/perf_endure.py:978: sort_button.click()
On 2012/08/02 23:11:34, Nirnimesh wrote:
> twice?

yes, once to open the sort menu and once to close it.  it seems kinda hacky, but
doing this causes two divs to be added to the DOM that are used in lines 989 and
1000 below.

[Nirnimesh, 2012-08-02 23:56:12]

LGTM

[commit-bot: I haz the power, 2012-08-02 23:58:28]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/dennisjeffrey@chromium.org/10825166/1

[commit-bot: I haz the power, 2012-08-02 23:59:57]

Change committed as 149751