Mobile Web Test Suites Working Group
News · Deliverables · Existing test suites · Logistics · References
The mission of the MWI Test Suites Working Group is to help create a strong foundation for the mobile Web through the development of a set of test suites targeted at browsers.
These test suites can help assess which technologies and which features of a given technologies are supported in existing browsers on mobile devices.
Contribute
To help establish browsers support charts based on existing test suites, please put your mobile web browser through the tests suites available in our mobile-friendly test harness, which automatically collects results as you go.
Do you know of a specific Web technology or combinations of Web technologies with poor interoperability on mobile devices? Let us know on public-mwts@w3.org and we'll see if we can come up with good test cases for it.
You can also contribute improvements to the test harness since it is released as an open-source project on the W3C public CVS repository.
If you are an individual willing to commit some part of your time to help develop the test suites described below, please get in touch with Dominique Hazael-Massieux <dom@w3.org> as you may be eligible to become Invited Expert in this group.
If you are a W3C Member employee, learn how to join this Working Group.
News
June 30, 2009: minutes of June 30 teleconf: Widgets testing
June 23, 2009: minutes of June 23 teleconf: Widgets testing
June 16, 2009: minutes of June 16 teleconf: Widgets testing
June 9, 2009: minutes of June 9 teleconf
May 26, 2009: minutes of May 26 teleconf: Memory test
May 19, 2009: minutes of May 19 teleconf: Widgets testing, Memory test, WCTBM2 proposal
May 12, 2009: Publication of Guidelines for writing device independent tests as a Working Group Note.
May 12, 2009: minutes of May 12 teleconf: Widgets testing, Memory test
May 5, 2009: minutes of May 5 teleconf: Web compatibility test, Device Independence Testing guidelines
April 28, 2009: minutes of April 28 teleconf: Widgets testing, Web compatibility test, Device Independence Testing guidelines
April 14, 2009: minutes of April 14 teleconf: Web compatibility test
Deliverables
Ongoing work
- development of guidelines to create device-independent tests (CVS history)
- development of tests for W3C Widgets specs, cookies
- collaboration with OMA on sharing test suites:
- completing the existing WCSS test suites to cover CSS MP 2.0: additional test cases
- coverage analysis of SVG Tiny 1.2 test suite: draft analysis (transmitted to SVG WG)
- improvements to the mobile test harness
Test suites
- Conformance Test Suites
- See our survey of conformance test suites produced by W3C and OMA Working Groups
- our mobile-friendly version of the DOM Level 1 test suite based on the original DOM Test suites
- our additional test cases for CSS MP 2.0
- our test cases for CSS Media Types
- our test cases for XHTML Forms
- our Web Compatibility Test for Mobile Browsers (WCTMB) and its manifesto
- a test of memory limits in mobile browsers
- Elsewhere
- Opera's cookies test suites
- mobile ACID tests
- mobile AJAX
- Javascript support
- URI schemes and VCard support
- multimedia support
- support for XHTML Basic 1.1 new features and CSS Media Types
- support for encoding declarations techniques
- Test of what Accept Headers are sent on subrequests (images, CSS)
- HTML and CSS styling
- per-URI caching behavior
- PUKUPI tests for mobile browsers (goals)
- WURFL test suite
- MobileTech.mobi AJAX test suite
- Mobile Browser Concurrency Test, from Cloud Four
- Object loading
- Are images loaded when display:none?
We have integrated some of the test suites above in our Mobile Test Harness: you can help improve the knowledge about your browser by going through these test suites in this tool!
Tools
- Mobile Test Harness
- The Mobile Test Harness is a framework that can host Web-based test suites, allowing for a simple navigation from one test cases to the other, while recording results submitted by the user; the code of the harness is available as an open-source project
See also other W3C QA Tools.
Logistics
We use Tracker to track issues and action items.
We are meeting weekly on the phone during one hour, on Tuesdays, at 5pm CET / 11 am ET / 8am PT.
The teleconference bridge ("Zakim") is reachable at +1.617.761.6200 (numbers in France and the UK also available), with the teleconference code 8794.
In addition to the phone, we use the W3C IRC server on channel #mwts to scribe and communicate written information:
trackbot, start meeting Agenda: uri Chair: chair Regrets: regrets
See also RRSAgent documentation, Zakim bot documentation, Trackbot documentation.
References
Liaisons
Wilhelm Andersen , Opera, and Dominique Hazaël-Massieux, W3C, <dom@w3.org>, co-Chairs$Id: Overview.html,v 1.219 2009/06/30 15:22:47 dom Exp $
The running of this working group is supported by the European Union's 7th Research Framework Programme (FP7)
through the MobiWeb 2.0
Project, and its set up was funded through the 3GWeb European Project.