Closed Bug 794451 Opened 13 years ago Closed 13 years ago

Investigate if opening/closing of windows does not reset the global timeout in Mozmill

Categories

(Mozilla QA Graveyard :: Mozmill Tests, defect)

Product:
Mozilla QA Graveyard
Component:
Mozmill Tests
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED INVALID

People

(Reporter: vladmaniac, Unassigned)

References

(
URL
)

Details

We want to setup a larger default delay in endurance tests for the testTabbedBrowsing_OpenAndCloseMultipleWindows and if we reach 6s we get a disconnect. See https://bugzilla.mozilla.org/show_bug.cgi?id=788531#c9 We want to see if opening and closing new windows resets the global timeout in Mozmill or not. Normally, other actions like clicking would reset it.
URL: http://hg.mozilla.org/qa/mozmill-auto...
OS: Linux → All
Hardware: x86 → All
Blocks: 788531
I'm sure this bug is unnecessary because the real problem here is in Mozmill as pointed out on bug 788531 already. waitFor() doesn't send a passing frame via JSBridge. So lets get this fixed in Mozmill.
Component: Mozmill Automation → Mozmill
Product: Mozilla QA → Testing
Based on comment 1 I've switched this to the Testing Product -> Mozmill Component
Moving this bug over to Mozmill doesn't make sense. Please lets get a new bug filed for exactly this purpose. It should block this one.
Component: Mozmill → Mozmill Tests
Product: Testing → Mozilla QA
Not sure if I was even right with my suspicion. You should test it first before filing a new bug.
Opening and closing windows is not the issue, it's that we are using mozmill.utils.waitFor when closing the windows. This method does not appear to keep the connection alive. See bug 711360 comment 104
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → INVALID
Product: Mozilla QA → Mozilla QA Graveyard
You need to log in before you can comment on or make changes to this bug.