- From: Ian Davis <Ian.Davis@talis.com>
- Date: Mon, 20 Mar 2006 13:44:55 -0000
- To: "Maciej Stachowiak" <mjs@apple.com>, "Web APIs WG \(public\)" <public-webapi@w3.org>
- Message-ID: <DD5E887552496241BC701548837A282F02C26B53@nemo.talis.local>
Maciej, The test suite is a great piece of work. I have question and a suggestion: in the test suite you have the following directory structure: /WindowTestSuite ecmascript browsing-contexts publish html browsing-contexts shared browsing-contexts svg browsing-contexts xhtml browsing-contexts scripts Some of the code in ecmascript/browsing-contexts is repeated underthe publish/shared/browsing-contexts directory. Which is the canonical form? I'm guessing it's the one in ecmascript. The publish/shared directory contains some test harness code too which is cool. The html, svg and xhtml directories play the role of test harnesses for various ecmascript hosts. Presumably we'd accept contributions from people who want to write harnesses for other bindings and hosts. Is there a better structure to help with this? Perhaps the first subdirectory of the test suite should be the binding with subdirectories for the harnesses and actual tests. Maybe something like: /WindowTestSuite ecmascript harnesses shared html svg xhtml tests browsing-contexts The test assertion framework should come out of this tree into a separate area for reuse by other components e.g. XHR. I've already rewritten my XHR method tests to use it so we're consistent. I'd like to be consistent on the directory structure too. Ian To find out more about Library 2.0 and the Challenge of Disruptive Innovation, we invite you to read the latest white paper, listen to Talis' new Library 2.0 Gang podcasts and engage with us. Visit: www.talis.com/resources and www.talis.com/podcasts Any views or personal opinions expressed within this email may not be those of Talis Information Ltd. The content of this email message and any files that may be attached are confidential, and for the usage of the intended recipient only. If you are not the intended recipient, then please return this message to the sender and delete it. Any use of this e-mail by an unauthorised recipient is prohibited.
Received on Monday, 20 March 2006 13:42:38 UTC