On Sat, Jul 9, 2011 at 2:30 AM, Ashar Voultoiz <hashar+wmf(a)free.fr> wrote:
* Safari, Opera & Mozilla for mobile : they are
probably mostly the same
as the desktop version. I have not found emulators for them.
* Android : has an emulator. On my computer it is painfully slow and not
usable for anything.
* Blackberry : emulator is Windows only :-/
Would be great to enhance our testswarm with more browsers. Maybe we
could contact those mobiles developers to connect to our testswarm?
Note also that there'll be at least three distinct things we want to test on
the mobile browsers:
* JS & browser interactive behavior _of MediaWiki_
* JS & browser interactive behavior _of the alternate mobile view_
(MobileFrontend, on track to replace the current mobile. and m. gateways)
* default redirection to the appropriate view based on device
For the MediaWiki JS tests on Mobile Safari, Android default browser,
Blackberry default browser, Opera Mobile, etc we should only need to add
those browsers to the job submissions going into TestSwarm so it'll farm the
tests out to any connected clients -- currently Krinkle manages how that's
set up.
However for the most part, Mobile Safari, default Android browser, Opera
Mobile, and Firefox for Android should work _about the same_ as their
desktop equivalents, with the same modern JavaScript engines etc. There will
be some differences in JavaScript & HTML support (for instance, the Android
browser doesn't support SVG until 3.0) but this is unlikely to trip up much
in the core JS tests.
More relevant in most cases will probably be UI tests, like making sure that
various links and buttons are in visible, clickable areas of the screen; we
don't have any of these tests yet using QUnit.
Anything related to MobileFrontend will need to have a test suite created
for it; note that for less-capable devices, TestSwarm's client-side
JavaScript system probably won't actually work (certainly it won't for Opera
Mini!)
Redirection tests again might need another test harness infrastructure.
-- brion