Section 2.2.4 - WebDriver (Karl Groves)

[darthcav]

Reference

http://lists.w3.org/Archives/Public/public-wai-ert-tools/2014Jul/0005

Original Comment

The inclusion of WebDriver in this section is excellent, however many other options exist. WebDriver truly excels at performing “tests that automate the application's and the end-users' behaviour.” In doing so, WebDriver can help to automate acceptance testing which relies on user interaction to trigger specific UI states that a webcrawler could not trigger on its own. But this is neither the only tool for introspection or for test automation. Many unit test frameworks exist which could be utilized for accessibility testing. While I acknowledge W3C’s desire to be vendor neutral, it does seem prudent that the existence of such frameworks be acknowledged. It would also be prudent to mention that accessibility testing can be performed as part of/ in conjunction with nearly any unit test or acceptance testing framework.

[nitedog]

Proposed Resolution

Accept - If we list one example then we should list 1-2 others as well. Also need to better frame with "such as" or "including" etc.

[ysmartin]

I understood the commenter in a different sense. The issue is not that WAET is providing one example and should be providing more; it is that WAET is providing a vendor-neutral spec (i.e. WebDriver) without listing any specific test framework product.

[darthcav]

Resolution

Partial - reword section 2.2.4: There are [several?] tools that enable developers to write tests that automate the application's and the end-users' behaviour. There is an effort to standardize a common API for such tools, one of these APIs is the W3C WebDriver API [WebDriver]