- From: Larry Masinter <masinter@adobe.com>
- Date: Tue, 18 Mar 2014 20:21:17 +0000
- To: Philippe Le Hegaret <plh@w3.org>, Andreas Tolfsen <ato@mozilla.com>
- CC: "public-test-infra@w3.org" <public-test-infra@w3.org>, Jacob Goldstein <jacobg@adobe.com>, "jgraham@mozilla.com" <jgraham@mozilla.com>
I'm not sure what the use case is for WebDriver. The three use cases I have in mind, using WebDriver has some disadvantages, doesn't it? If it can't be used with older browsers? * validating a report of an implementation of a spec feature * verifying that conformance requirements in the spec can be tested * determining which deployed implementations implement a feature perhaps you could use an automated test for testing an implementation, but it would need special setup for testing new devices on embedded controllers anyway. > Agreed. That's usual dilemma between writing human tests now or waiting > a year or two for WebDriver testing to be good enough to be used in wpt > (and wptserve?). don't wait. test the web now.
Received on Tuesday, 18 March 2014 20:21:51 UTC