• June 24, 2011
• June 10, 2011
• June 03, 2011
• May 26, 2011
• May 18, 2011
• May 11, 2011

What do we need? - binary extension grafxbot? - zippity server?

grafx bot testing harness mochitest

test harness talos tests take a javascript file, run as a browser-chrome test, inject unit tests assertion specialpowers working is difficult, disabling/reenabling is hard

what info do we need from the phones - retreive gfx hardware, ditch the hardware component from grafxbot

It needs a different UI - reporting to django mysql database, web: http://brasstacks.mozilla.com/resultserv/data/results/f880a3e6-aabb-4ef0-aba0-6baa0a53bae0 example

- website in the browser

mfinkle sanity test on the server

mfinkle

- zippity based on google app engine - no webpage setup to view the data - most difficult issue: getting mochitest framework working - mochitests need different view for data (need server side patch) - zippity should be able to scale

- joel packaged mochikit.jar (340kb) - test bundle is 1.35 MB

we don't want to have bad test that crash the phone

- run mochitest-plain remotely

jmaher: what extension - add to test harness extension install extension local at the least, results server

jmaher: dom-level-1, dom-level-2 core.

too small window Fennec for reftests, dougt wrote a patch for that.

make documentation for automation that I mailed to AaronMT

put it on a wiki page, not on scrumpad - draft ready by the end of the week. (tony wants to talk about it in Romania)

Mochitest: dom-level-1, dom-level-2 and mochitest-plain reftests: border-radius