This shows you the differences between two versions of the page.
Next revision | Previous revisionNext revisionBoth sides next revision | ||
test:harness [2008/04/21 12:16] – created fantasai | test:harness [2009/11/30 12:33] – fantasai | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== Browseable Test Harness ====== | ====== Browseable Test Harness ====== | ||
- | Dominique Hazael-Massieux | + | In 2007, Dominique Hazael-Massieux created a CGI-based harness for the Mobile Web Initiative' |
- | See [[http:// | + | An easy-to-use harness for reporting tests like this would be useful across all of W3C's Interaction Domain working groups. It has the potential to make the process of creating implementation reports much, much easier, and it would allow more involvement from the community outside W3C. |
+ | |||
+ | The CSS Working Group planned to extend this harness and use it for the CSS conformance tests and implementation reports. HP took Dominique' | ||
+ | |||
+ | The current state of the project is that nobody here knows how the harness works, whether it's reliable, or how to set it up with a new set of tests. The reporting half of the improvements were not implemented, | ||
+ | |||
+ | The source code, bug database, and prototype URL are all listed below. If you are interested in taking ownership of this project, and have any questions, please contact the [[http:// | ||
===== Harness Resources ===== | ===== Harness Resources ===== | ||
Line 9: | Line 15: | ||
* [[http:// | * [[http:// | ||
* [[http:// | * [[http:// | ||
+ | * [[http:// | ||
+ | * [[http:// | ||
+ | * [[http:// | ||
===== Harness Wishlist ===== | ===== Harness Wishlist ===== | ||
Line 39: | Line 48: | ||
* (7) Ability to delete all data for a given test (so that when a test is changed we can invalidate the results for that test). This process could be triggered manually on the command line rather than via CGI---that avoids the need for a login system. | * (7) Ability to delete all data for a given test (so that when a test is changed we can invalidate the results for that test). This process could be triggered manually on the command line rather than via CGI---that avoids the need for a login system. | ||
+ | |||
+ | ===== Other Notes ===== | ||
+ | |||
+ | * Put requirements up front | ||
+ | * Add Skip button | ||
+ | * Track session so that a bad user's data can be deleted | ||