Integrate the Leak Gauge Upload and Result Form into AMO

RESOLVED WONTFIX

Status

enhancement
P5
normal
RESOLVED WONTFIX
12 years ago
4 years ago

People

(Reporter: cbook, Unassigned)

Tracking

unspecified
Future

Details

()

Hi

currently we have for Extension Developers and Editors a Leak Gauge Upload & Result Form on http://mxr.mozilla.org/mozilla/source/tools/footprint/leak-gauge.html

We would like to have this on a AMO Page, so that Extension Devs and AMO Editors can use the Form also from an AMO Page.

Very nice would be when this would have a kind of indicator depend on Leak or Non-Leak Output when the Leak Log is processed. (see http://wiki.mozilla.org/QA:Home_Page:Firefox_3.0_TestPlan:Leaks:LeakTesting-How-To#The_Leak_Gauge_Leak_Log_File for an example).

There is no rush for this, but we would like to get this on AMO's Radar.
Nick, fligtar:  is this something we want to put in the dev hub?  It's just JS.
Priority: -- → P5
Target Milestone: --- → 4.x (triaged)
Component: Public Pages → Developer Pages
QA Contact: web-ui → developers
Whiteboard: [ddn]
Whiteboard: [ddn]
Target Milestone: 4.x (triaged) → Future
Basta - would this fit into the validator easily?
I don't think so. From what I understand, the script requires a period of data collection from a browsing session; we could emulate it on the server, but the add-on would need to be installed and a significant amount of time would need to pass for the test(s) to complete.

Perhaps it could be done using some type of Selenium integration, however, the data it would gather would not be available with the immediacy that the validator implementation currently requires.
Thanks for filing this.  In an effort to not drown in existing reports we're aggressively closing old enhancements and bugs to get the buglist to a reasonable level so we can scope and process bug sprints in an effective manner.

Patches for this bug are still welcome.
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → WONTFIX
Product: addons.mozilla.org → addons.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.