625764 - Could not validate element ID: status with text disabled in testDisableEnablePlugin.js

Status: RESOLVED FIXED

(Mozilla QA Graveyard :: Mozmill Tests, defect)

Description

[Henrik Skupin [:whimboo][⌚️UTC+1]]

Module:    /testAddons/testDisableEnablePlugin.js
Test:      testDisableEnablePlugin    
Failure:   Error("could not validate element ID: status with text disabled (testDisableEnablePlugin.js:82)
Branches:  1.9.2, 1.9.1
Platforms: Linux

Could also be related to 'Method with name: 'OpenBrowserWindow' is not in any open window' in the following result:

http://mozmill-release.brasstacks.mozilla.com/#/general/failure?branch=3.5&platform=Linux&test=firefox%2FtestAddons%2FtestDisableEnablePlugin.js&func=setupModule

Started to occur on 110707. We should check if anything has been checked in between those two builds.

Dave, do you have interest to work on it?

Comment 1

[Aaron Train [:aaronmt]]

Just from looking at the code, I think this is just a stale element declared before the page is loaded so we have a bad reference during assertText, and then needs to be reassigned after loading the page again.

http://hg.mozilla.org/qa/mozmill-tests/file/f96529b1547e/firefox/testAddons/testDisableEnablePlugin.js#l78

Comment 2

[Aaron Train [:aaronmt]]

Attachment: Patch v1 - (1.9.2)

Get a valid reference to the 'status' element after page load, and reassign after page load again.

Comment 3

[Henrik Skupin [:whimboo][⌚️UTC+1]]

I wonder why it has been started last Monday. It should have been happening already for a long time.

Comment 4

[Henrik Skupin [:whimboo][⌚️UTC+1]]

Comment on attachment 504501 [details] [diff] [review]
Patch v1 - (1.9.2)

Makes sense so lets see how it changes the behavior of the test. Not sure if it is enough.

Comment 5

[Aaron Train [:aaronmt]]

Landed as

1.9.2 - http://hg.mozilla.org/qa/mozmill-tests/rev/7a6faa7bddf8
1.9.1 - http://hg.mozilla.org/qa/mozmill-tests/rev/556aba82c142

I'll keep an eye out next few day, and keep this open