Closed Bug 1363373 Opened 7 years ago Closed 7 years ago

For quantum pageload tests, browse to playback URL during Firefox initialization

Categories

(Testing :: Talos, enhancement)

Version 3
enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: rwood, Assigned: rwood)

References

Details

(Whiteboard: [PI:June])

Attachments

(1 file)

For quantum-pageloader tests, after mitmproxy server playback has started, we want to browse to the pageload URL(s) during the initial Firefox initialization phase (before the test actually starts). Then Firefox is shutdown and restarted (as per normal behaviour) before the actual pageload test begins.
Will add this once the main foundation of the talos quantum-pageloader tests has landed
Status: NEW → ASSIGNED
So my plan is to add some js in testing/talos/talos/mitmproxy that will browse to each of the test URLs once. Then I'm thinking the best place to call this would be in the talos init page (testing/talos/talos/getInfo.html). I'll need to have getInfo.html receive a URL param indicating if the test uses mitmproxy, and if so invoke the js. :jmaher, what do you think?
Flags: needinfo?(jmaher)
I think this is ok- also since we are using marionette during initialization in some tests, this might be easy with some marionette commands.  Looking forward to a patch for this.
Flags: needinfo?(jmaher)
It is certainly possible to use the Marionette remote protocol to load
pages.  Normally it waits for the DOMContentLoaded event to fire before
returning from navigation, but it has recently been possible to set the
pageLoadStrategy capability to "none" in order to return immediately
after navigation.
(In reply to Andreas Tolfsen ‹:ato› from comment #4)

Thanks for the tip!
Whiteboard: [PI:June]
After discussing this with :jmaher, I realize this really isn't necessary. The idea here was to make sure everything required for the site playback is read from the mitmproxy archive into the browser cache first, and then just measure subsequent pageloads. However we are already ignoring the first 5 quantum-pageload measurements anyway, so the first measurement (which is significantly higher) is ignored anyway.
Status: ASSIGNED → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: