- From: John Jansen <John.Jansen@microsoft.com>
- Date: Tue, 9 Jun 2015 18:09:05 +0000
- To: James Graham <james@hoppipolla.co.uk>, "public-browser-tools-testing@w3.org" <public-browser-tools-testing@w3.org>
Agreed. I am doing work to verify two things: 1. The current tests actually test the spec as it exists today 2. All 'Must' statements in the spec have corresponding tests The first exercise is challenging because there is no good mapping between test and spec statement. The second exercise is something that should have been done for HTML5 or some other spec already, so I've been looking around the w3c for solutions. If anyone knows of a good solution that could be leveraged, please let me know. -----Original Message----- From: James Graham [mailto:james@hoppipolla.co.uk] Sent: Tuesday, June 9, 2015 10:11 AM To: public-browser-tools-testing@w3.org Subject: State of the testsuite As far as I know the testsuite has not tracked recent changes to the spec. This is obviously something that needs to be fixed, but in the short term I advise not putting too much weight on tests you have not personally cross-checked against the actual specification.
Received on Tuesday, 9 June 2015 18:09:34 UTC