Hi, We should start working in the definition of a test suite for the spec. Andrei has recently contributed the tests used in Google Gears which is a good starting point. We would urge other members to contribute their test cases in order to define a complete test suite for the spec. Regarding the format... I have found this interesting document proposing the format and the way of performing the whole testing process: http://www.w3.org/QA/WG/2005/01/test-faq >From this document.... a good test is: - Mappable to the specification (you must know what portion of the specification it tests) - Atomic (tests a single feature rather than multiple features) - Self-documenting (explains what it is testing and what output it expects) - Focused on the technology under test rather than on ancillary technologies - Correct According to this guidelines, I think the optimal format could be a HTML+JavaScript file containing a single test case. This web page should contain an explanation of what is being tested and the expected output of the JS code when executed within the browser. There a lot of complete test suites form other W3C specs that can be checked, SVG tests could be a good example of what we could deliver: http://www.w3.org/Graphics/SVG/Group/repository/testsuite/1.1/htmlEmbedHarness/ Any thoughts on this? Any volunteers to contribute tests or to define a common pattern for this files? - AngelReceived on Tuesday, 10 March 2009 12:18:29 UTC
This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:50:54 UTC