Closed Bug 747515 Opened 12 years ago Closed 7 years ago

Add a self-serve web interface for running Eideticker tests against a particular build

Categories

(Testing Graveyard :: Eideticker, defect)

All
Android
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: wlach, Unassigned)

References

()

Details

(Whiteboard: [eideticker:p1])

It would be useful if developers could run tests and analyze results without needing to ssh into the machine and invoke bizarre command-line incantations. Ideal would be a web-based from that they could use to submit an apk and a set of tests that they'd like to run, with results both emailed and available in a nice-looking web ui.
Summary: Add a self-serve interface for running Eideticker tests against a particular build → Add a self-serve web interface for running Eideticker tests against a particular build
Whiteboard: [eideticker:p1]
Related to bug 770144 and wanting to run with custom build. How hard would it be to add a temporary privileged solution to run a custom build, optional change the default prefs and get a result out with a profile+video? Something over SSH for a few trusted individuals is fine.
(In reply to Benoit Girard (:BenWa) from comment #1)
> Related to bug 770144 and wanting to run with custom build. How hard would
> it be to add a temporary privileged solution to run a custom build, optional
> change the default prefs and get a result out with a profile+video?
> Something over SSH for a few trusted individuals is fine.

Not hard, maybe an (undisturbed) day or two of effort. Probably need to:

(1) Refactor the profiling code to not be tied to the dashboard
(2) Make the graph view of results (http://people.mozilla.com/~wlachance/cnn-benchmark/metric.html?data=metric-test-1343419943.79.json#/checkerboard) be more intuitive to create
(3) Add profiling information to the graph view of results
(4) Add option to change preferences
BenWa pointed out that just doing (1) and (4) would probably be enough to help him and :Cwiiis  with their updates to incremental tiled rendering.

Patch addressing (1): https://github.com/mozilla/eideticker/commit/66b51a08f1a408efb9d4f8b6c0857cac3a039ed3

I'll add something for (4) shortly.
Ok you can now specify command line arguments like this:

runtest.py --no-capture --extra-prefs "{\"layers.acceleration.frame-counter\": true }" org.mozilla.fennec src/tests/ep1/taskjs.org/index.html
(In reply to William Lachance (:wlach) from comment #4)
> Ok you can now specify command line arguments like this:
> 
> runtest.py --no-capture --extra-prefs
> "{\"layers.acceleration.frame-counter\": true }" org.mozilla.fennec
> src/tests/ep1/taskjs.org/index.html

Nice!  Thank you!!
Dave Hunt has some ideas for getting jenkins to do this.
URL:
Flags: needinfo?(dave.hunt)
Jenkins supports parameterised build, so we could create a job that takes the build location URL as a parameter. The job would then download the build from that location and run the tests. We could add e-mail notifications of the results (with attachments), and Jenkins could also serve as the results dashboard. As this bug appears to be related to Firefox for Android, this proposal will depend on bug 1015382. It would be useful to identify a typical command line for one of these adhoc tests.
Flags: needinfo?(dave.hunt)
Eideticker has been discontinued, see bug 1361056
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
Product: Testing → Testing Graveyard
You need to log in before you can comment on or make changes to this bug.