367559 - get pageloader extension checked in to mozilla CVS

Status: RESOLVED FIXED

(Release Engineering :: General, defect)

Description

[Robert Helmer [:rhelmer]]

Attachment: pageloader version 0.5 xpi, includes makefile and unit tests

I've put together a pageloader extension, which we can use to drive the Tp test from chrome (instead of having both the driver and test itself run in content).

This version is intended to be run like:

firefox -chrome chrome://pageloader/content/pageloader.xul

This tests just the rendering engine without any browser.xul/browser.js, and prompts the user for a list of URLs to load.

Comment 1

[Rob Campbell [:rc] (:robcee)]

Comment on attachment 252117 [details]
pageloader version 0.5 xpi, includes makefile and unit tests

I'm assuming this is a work in progress. Page cycling seems to work, though I was getting security warnings in a fresh profile that would prevent it from running unattended.

Comment 2

[Robert Helmer [:rhelmer]]

Thanks! Is testing/tools/pageloader an OK location?

On the security warnings (clarified in irc that these were SSL warnings from websites) - right, we need changes in the profile for unattended operation, including turning dump() on. I'll document that stuff soon, probably just in a README file.

The other big blocker for unattended operation is specifying the list of URLs to load from on the command line, rather than prompting the user. Also, it should be possible to pass a switch on the command line to autostart, instead of requiring the user to press the Start button.

Comment 3

[Rob Campbell [:rc] (:robcee)]

Absolutely that is an ok location. Feel free to checkin at your convenience.

Those are definitely important options for automating this. You could checkout the way reftest adds its command line options as a starting point.

Comment 4

[Robert Helmer [:rhelmer]]

Landed, thanks!