W3C home > Mailing lists > Public > public-mwts@w3.org > January 2007

What test suites to develop

From: Rosenthal, Lynne <lsr@email.nist.gov>
Date: Tue, 16 Jan 2007 11:46:27 -0500
Message-ID: <60DE4C815920CA41AF6CC5CFDA9CC849039E29D6@WSXG03.campus.nist.gov>
To: <member-mwts@w3.org>, <public-mwts@w3.org>
Key to the deliverables for the group is 'What test suites and tools
should the group develop?'


When the group was being created, it was thought that a test suite would
consist of a catalog of existing test suites that would be applicable to
mobile web devices - e.g., SVG tiny, parts of CSS, etc.  Carmelo put
together a prototype of what such a catalog could look like.  This type
of catalog may be nice to have, but it is of limited use since it
doesn't provide a way to test the device as a whole.  But, it is
something that we could produce quickly and have a deliverable early in
the WG's existence.


What are really needed are test suites or tools that would test the
device as a whole - not just individual pieces running on the device.
The essential first step in doing this is to have a set of requirements
for which the tests/tools would test for.  So, that is the big question
- is there a set of requirements that the WG can target or does the WG
need to develop such a specification?



Received on Tuesday, 16 January 2007 16:46:39 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:08:01 UTC