Browser Testing and Tools Working Group Charter Extended

Dear members of the Browser Testing and Tools Working Group,

I'm relaying the message to the Working Group's primarily public mailing 
list, to notify the group that its current charter is now extended to 30 
September 2017.

Best regards,
Xueyuan



-------- Forwarded Message --------
Subject:  WebDriver is a W3C Candidate Recommendation; Charter Extended 
(Call for Implementations and Review)
Date:  Thu, 30 Mar 2017 22:16:23 +0800
From:  Xueyuan Jia <xueyuan@w3.org>
To:  w3c-ac-members@w3.org
CC:  chairs@w3.org



Dear Advisory Committee Representative,
Chairs,

I am pleased to announce that WebDriver is now a W3C Candidate
Recommendation:
   https://www.w3.org/TR/2017/CR-webdriver-20170330/

[...]

The Browser Testing and Tools Working Group Charter is hereby extended
until 30 September 2017:
   https://www.w3.org/2016/05/browser-testing-tools-charter.html

The WebDriver specification is expected to exit CR in the extension
timeframe.

[...]

Thank you,

For Tim Berners-Lee, Director, and
Michael[tm] Smith, Browser Testing and Tools WG Team Contact;
Xueyuan Jia, W3C Marketing & Communications

==============================================
Quoting from
WebDriver
W3C Candidate Recommendation 30 March 2017

This version:
   https://www.w3.org/TR/2017/CR-webdriver-20170330/
Latest published version:
   https://www.w3.org/TR/webdriver/

Abstract:
WebDriver is a remote control interface that enables introspection and
control of user agents. It provides a platform- and language-neutral
wire protocol as a way for out-of-process programs to remotely instruct
the behavior of web browsers.

Provided is a set of interfaces to discover and manipulate DOM elements
in web documents and to control the behavior of a user agent. It is
primarily intended to allow web authors to write tests that automate a
user agent from a separate controlling process, but may also be used in
such a way as to allow in-browser scripts to control a — possibly
separate — browser.

The standard forms part of the Web Testing Activity that authors a
larger set of tools commonly used for testing.

Status of This Document:
This section describes the status of this document at the time of its
publication. Other documents may supersede this document. A list of
current W3C publications and the latest revision of this technical
report can be found in the W3C technical reports index at
https://www.w3.org/TR/.

This Candidate Recommendation will have met its CR exit criteria when
there are at least two interoperable implementations of each feature in
the spec, as demonstrated in a (yet to be developed) implementation report.

This document was published by the Browser Testing and Tools Working
Group as a Candidate Recommendation. This document is intended to become
a W3C Recommendation. If you wish to make comments regarding this
document, please send them to public-browser-tools-testing@w3.org
(subscribe, archives). W3C publishes a Candidate Recommendation to
indicate that the document is believed to be stable and to encourage
implementation by the developer community. This Candidate Recommendation
is expected to advance to Proposed Recommendation no earlier than 30
April 2017. All comments are welcome.

Please see the Working Group's implementation report.

Publication as a Candidate Recommendation does not imply endorsement by
the W3C Membership. This is a draft document and may be updated,
replaced or obsoleted by other documents at any time. It is
inappropriate to cite this document as other than work in progress.

This document was produced by a group operating under the 5 February
2004 W3C Patent Policy. W3C maintains a public list of any patent
disclosures made in connection with the deliverables of the group; that
page also includes instructions for disclosing a patent. An individual
who has actual knowledge of a patent which the individual believes
contains Essential Claim(s) must disclose the information in accordance
with section 6 of the W3C Patent Policy.

This document is governed by the 1 March 2017 W3C Process Document.
==============================================