-
Notifications
You must be signed in to change notification settings - Fork 58
/
browser-testing-tools.html
524 lines (465 loc) · 22.6 KB
/
browser-testing-tools.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
<!DOCTYPE html>
<html lang="en-US">
<head>
<meta charset="utf-8">
<title>Browser Testing and Tools Working Group Charter</title>
<link rel="stylesheet" href="https://www.w3.org/2005/10/w3cdoc.css" type="text/css" media="screen">
<link rel="stylesheet" type="text/css" href="https://www.w3.org/OldGuide/pubrules-style.css">
<link rel="stylesheet" type="text/css" href="https://www.w3.org/2006/02/charter-style.css">
<style>
main {
max-width: 60em;
margin: 0 auto;
}
ul#navbar {
font-size: small;
}
dt.spec {
font-weight: bold;
}
dt.spec new {
background: yellow;
}
ul.out-of-scope > li {
font-weight: bold;
}
ul.out-of-scope > li > ul > li{
font-weight: normal;
}
.issue {
background: cornsilk;
font-style: italic;
}
.todo {
color: #900;
}
footer {
font-size: small;
}
</style>
</head>
<body>
<header id="header">
<aside>
<ul id="navbar">
<li><a href="#scope">Scope</a></li>
<li><a href="#deliverables">Deliverables</a></li>
<li><a href="#success-criteria">Success Criteria</a></li>
<li><a href="#coordination">Coordination</a></li>
<li><a href="#participation">Participation</a></li>
<li><a href="#communication">Communication</a></li>
<li><a href="#decisions">Decision Policy</a></li>
<li><a href="#patentpolicy">Patent Policy</a></li>
<li><a href="#licensing">Licensing</a></li>
<li><a href="#about">About this Charter</a></li>
</ul>
</aside>
<p>
<a href="https://www.w3.org/"><img alt="W3C" height="48" src="https://www.w3.org/Icons/w3c_home" width="72"></a>
</p>
</header>
<main>
<h1 id="title">PROPOSED Browser Testing and Tools Working Group Charter</h1>
<!-- delete PROPOSED after AC review completed -->
<p class="mission">The <strong>mission</strong> of the <a href="https://www.w3.org/testing/browser/">Browser Testing and Tools Working Group</a> is to
produce technologies for automating testing of Web applications running in browsers.</p>
<div class="noprint">
<p class="join"><a href="https://www.w3.org/2004/01/pp-impl/49799/join">Join the Browser Testing and Tools Working Group.</a></p>
</div>
<p style="padding: 0.5ex; border: 1px solid green"> This proposed charter is available
on <a href="https://github.com/w3c/charter-drafts/">GitHub</a>.
Feel free to raise <a href="https://github.com/w3c/charter-drafts/issues">issues</a>.
</p>
<table id=details class="summary-table">
<tr id="Duration">
<th>
Start date
</th>
<td>
TBD
</td>
</tr>
<tr id="CharterEnd">
<th>
End date
</th>
<td>
TBD + 2 years
</td>
</tr>
<tr>
<th>Charter extension</th>
<td>See <a href="#history">Change History</a>.
</td>
</tr>
<tr>
<th>
Chairs
</th>
<td>
David Burns, W3C Invited Expert
</td>
</tr>
<tr>
<th>
Team Contacts
</th>
<td>
<a href="mailto:mike@w3.org">Michael[tm] Smith</a> (0.05 <abbr title="Full-Time Equivalent">FTE</abbr>)
</td>
</tr>
<tr>
<th>
Meeting Schedule
</th>
<td>
<strong>Teleconferences:</strong> On an as-needed basis, up to once a week
<br>
<strong>Face-to-face:</strong> we will meet during the W3C's annual Technical Plenary week; additional face-to-face meetings may be scheduled by consent of the participants, usually no more than 3 per year.
</td>
</tr>
</table>
<section id="scope" class="scope">
<h2>Scope</h2>
<p>The scope of the Browser Testing and Tools Working Group includes protocols and APIs
for the purpose of automating testing of Web applications running in browsers—for example,
to simulate user actions such as clicking links, entering text, and submitting forms.</p>
</section>
<section id="deliverables">
<h2>
Deliverables
</h2>
<p><i>Draft state</i> indicates the state of the deliverable at the time of
the charter approval. The Working Group intends to publish the latest
state of their work as Candidate Recommendation and does not
intend to advance their documents to Recommendation (no explicit
milestones). The Group expects to continuously update the
Candidate Recommendation once it reaches that stage.</p>
<section id="normative">
<h3>
Normative Specifications
</h3>
<p>
The Working Group will deliver the following W3C normative specifications:
</p>
<dl>
<dt id="webdriver" class="spec"><a href="https://www.w3.org/TR/webdriver/">WebDriver</a></dt>
<dd>
<p>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.</p>
<p class="draft-status"><b>Draft state:</b> <a href="https://www.w3.org/TR/2020/WD-webdriver2-20200824/">Working Draft</a></p>
<p class="milestone"><b>Expected completion:</b> Candidate Recommendation Snapshots</p>
<p><b>Adopted Draft:</b> <a href="https://www.w3.org/TR/2020/WD-webdriver2-20200824/">WebDriver, W3C Working Draft 24 August 2020</a>
<p><b>Exclusion Draft:</b> <a href="https://www.w3.org/TR/2019/WD-webdriver2-20190912/">W3C, First Public Working Draft 12 September 2019</a>. Exclusion period <b>12-Sep-2019</b>; Exclusion period <b>09-Feb-2020</b>.
<p><b>Other Charter:</b> <a href="https://www.w3.org/2018/12/browser-testing-tools.html">https://www.w3.org/2018/12/browser-testing-tools.html</a>
</dd>
<dt id="webdriver-bidi" class="spec"><a href="https://w3c.github.io/webdriver-bidi/">WebDriver Bidirectional Protocol</a></dt>
<dd>
<p>The WebDriver Bidirectional Protocol extends WebDriver by introducing a bidirectional communication mechanism; in place of the strict command/response format of WebDriver, that bidirectional communication mechanism permits events to stream from the user agent to the controlling software, better matching the evented nature of the browser DOM.</p>
<p class="draft-status"><b>Draft state:</b> <a href="https://w3c.github.io/webdriver-bidi/">Editor's Draft</a></p>
<p class="milestone"><b>Expected completion:</b> Candidate Recommendation Snapshots</p>
</dd>
</dl>
</section>
<section id="ig-other-deliverables">
<h3>
Other Deliverables
</h3>
<p>
Other non-normative documents may be created such as:
</p>
<ul>
<li>Use case and requirement documents;</li>
<li>Test suite and implementation report for the specification;</li>
<li>Primer or Best Practice documents to support web developers when designing applications.</li>
</ul>
</section>
</section>
<section id="success-criteria">
<h2>Success Criteria</h2>
<p>Each specification should contain separate sections detailing all known security and privacy implications for implementers, Web authors, and end users.</p>
<p>There should be testing plans for each specification, starting from the earliest drafts.</p>
<p>To promote interoperability, all changes made to specifications should have <a href='https://www.w3.org/2019/02/testing-policy.html'>tests</a>.</p>
<p>All new features should be supported by at least two implementers stating their support for said feature before being incorporated in the specification.</p>
</section>
<section id="coordination">
<h2>Coordination</h2>
<p>For all specifications, this Working Group will seek <a href="https://www.w3.org/Guide/documentreview/#how_to_get_horizontal_review">horizontal review</a> for
accessibility, internationalization, performance, privacy, and security with the relevant Working and
Interest Groups, and with the <a href="https://www.w3.org/2001/tag/" title="Technical Architecture Group">TAG</a>.
Invitation for review must be issued during each major standards-track document transition, including
<a href="https://www.w3.org/Consortium/Process/#RecsWD" title="First Public Working Draft">FPWD</a>. The
Working Group is encouraged to engage collaboratively with the horizontal review groups throughout development of
each specification. The Working Group is advised to seek a review at least 3 months before first entering
<a href="https://www.w3.org/Consortium/Process/#RecsCR" title="Candidate Recommendation">CR</a> and is encouraged
to proactively notify the horizontal review groups when major changes occur in a specification following a review.</p>
<p>Additional technical coordination with the following Groups will be made, per the <a href="https://www.w3.org/Consortium/Process/#WGCharter">W3C Process Document</a>:</p>
<section>
<h3 id="w3c-coordination">W3C Groups</h3>
<dl>
<dt><a href="https://www.w3.org/2019/webapps/">Web Applications Working Group</a></dt>
<dd>This group facilitates the development of client-side web applications.</dd>
<dt><a href="/Style/CSS/">CSS Working Group</a></dt>
<dd>This group develops and maintains CSS.</dd>
<dt><a href="/2011/webtv/">Media and Entertainment Interest Group</a></dt>
<dd>This group provides a forum for media-related technical discussions to track progress of media features on the Web</dd>
<dt><a href="/WAI/APA/">Accessible Platform Architectures (APA) Working Group</a></dt>
<dd>This group ensures W3C specifications provide support for accessibility to people with disabilities, and
there is a possibility of relevant accessibility considerations in APIs for browser testing.</dd>
</dl>
</section>
</section>
<section class="participation">
<h2 id="participation">
Participation
</h2>
<p>
To be successful, this Working Group is expected to have 6 or more active participants for its duration, including representatives from the key implementors of this specification, and active Editors and Test Leads for each specification. The Chairs, specification Editors, and Test Leads are expected to contribute half of a working day per week towards the Working Group. There is no minimum requirement for other Participants.
</p>
<p>
The group encourages questions, comments and issues on its public mailing lists and document repositories, as described in <a href='#communication'>Communication</a>.
</p>
<p>
The group also welcomes non-Members to contribute technical submissions for consideration upon their agreement to the terms of the <a href="https://www.w3.org/Consortium/Patent-Policy/">W3C Patent Policy</a>.
</p>
<p>Participants in the group are required (by the <a href="https://www.w3.org/Consortium/Process/#ParticipationCriteria">W3C Process</a>) to follow the
W3C <a href="https://www.w3.org/Consortium/cepc/">Code of Ethics and Professional Conduct</a>.</p>
</section>
<section id="communication">
<h2>
Communication
</h2>
<p id="public">
Technical discussions for this Working Group are conducted in <a href="https://www.w3.org/Consortium/Process/#confidentiality-levels">public</a>: the meeting minutes from teleconference and face-to-face meetings will be archived for public review, and technical discussions and issue tracking will be conducted in a manner that can be both read and written to by the general public. Working Drafts and Editor's Drafts of specifications will be developed in public repositories and may permit direct public contribution requests.
The meetings themselves are not open to public participation, however.
</p>
<p>
Information about the group (including details about deliverables, issues, actions, status, participants, and meetings) will be available from the <a href="https://www.w3.org/testing/browser/">Browser Testing and Tools Working Group home page.</a>
</p>
<p>
Most Browser Testing and Tools Working Group teleconferences will focus on discussion of particular specifications, and will be conducted on an as-needed basis.
</p>
<p>
This group primarily conducts its technical work on the public mailing list <a id="public-name" href="mailto:public-browser-tools-testing@w3.org">public-browser-tools-testing@w3.org</a> (<a href="https://lists.w3.org/Archives/Public/public-browser-tools-testing/">archive</a>)
and on <a id="public-github" href="https://github.com/w3c/webdriver">GitHub issues</a>.
The public is invited to review, discuss and contribute to this work.
</p>
<p>
The group may use a Member-confidential mailing list for administrative purposes and, at the discretion of the Chairs and members of the group, for member-only discussions in special cases when a participant requests such a discussion.
</p>
</section>
<section id="decisions">
<h2>
Decision Policy
</h2>
<p>
This group will seek to make decisions through consensus and due process, per the <a href="https://www.w3.org/Consortium/Process/#Consensus"> W3C Process Document (section 3.3</a>). Typically, an editor or other participant makes an initial proposal, which is then refined in discussion with members of the group and other reviewers, and consensus emerges with little formal voting being required.</p>
<p>
However, if a decision is necessary for timely progress and consensus is not achieved after careful consideration of the range of views presented, the Chairs may call for a group vote and record a decision along with any objections.
</p>
<p>
To afford asynchronous decisions and organizational deliberation, any resolution (including publication decisions) taken in a face-to-face meeting or teleconference will be considered provisional.
A call for consensus (CfC) will be issued for all resolutions (for example, via email, GitHub issue or web-based survey), with a response period of <span id='cfc'>10 calendar days</span>, depending on the chair's evaluation of the group consensus on the issue.
If no objections are raised by the end of the response period, the resolution will be considered to have consensus as a resolution of the Working Group.
</p>
<p>
All decisions made by the group should be considered resolved unless and until new information becomes available or unless reopened at the discretion of the Chairs or the Director.
</p>
<p>
This charter is written in accordance with the <a href="https://www.w3.org/Consortium/Process/#Votes">W3C Process Document (Section 3.4, Votes)</a> and includes no voting procedures beyond what the Process Document requires.
</p>
</section>
<section id="patentpolicy">
<h2>
Patent Policy
</h2>
<p>
This Working Group operates under the <a href="https://www.w3.org/Consortium/Patent-Policy/">W3C Patent Policy</a> (Version of 15 September 2020). To promote the widest adoption of Web standards, W3C seeks to issue Web
specifications that can be implemented, according to this policy, on a Royalty-Free basis.
For more information about disclosure obligations for this group, please see the <a href="https://www.w3.org/2004/01/pp-impl/">W3C Patent Policy Implementation</a>.
</p>
</section>
<section id="licensing">
<h2>Licensing</h2>
<p>This Working Group will use the <a href="https://www.w3.org/Consortium/Legal/copyright-software">W3C Software and Document license</a> for all its deliverables.</p>
</section>
<section id="about">
<h2>
About this Charter
</h2>
<p>
This charter has been created according to <a href="https://www.w3.org/Consortium/Process/#GAGeneral">section 5.2</a> of the <a href="https://www.w3.org/Consortium/Process/">Process Document</a>. In the event of a conflict between this document or the provisions of any charter and the W3C Process, the W3C Process shall take precedence.
</p>
<section id="history">
<h3>
Charter History
</h3>
<p>The following table lists details of all changes from the initial charter, per the <a href="https://www.w3.org/Consortium/Process/#CharterReview">W3C Process Document (section 5.2.3)</a>:</p>
<table class="history">
<tbody>
<tr>
<th>
Charter Period
</th>
<th>
Start Date
</th>
<th>
End Date
</th>
<th>
Changes
</th>
</tr>
<tr>
<th>
<a href="http://www.w3.org/2011/08/browser-testing-charter">Initial Charter</a>
</th>
<td>
<i>13 October 2011</i>
</td>
<td>
<i>31 December 2013</i>
</td>
<td>
<i>No changes in scope or deliverables.</i>
</td>
</tr>
<tr>
<th>
Charter Extension
</th>
<td>
<i>1 January 2013</i>
</td>
<td>
<i>31 December 2015</i>
</td>
<td>
<i>No changes in scope or deliverables.</i>
</td>
</tr>
<tr>
<th>
Charter Extension
</th>
<td>
<i>1 January 2016</i>
</td>
<td>
<i>31 March 2016</i>
</td>
<td>
<i>No changes in scope or deliverables.</i>
</td>
</tr>
<tr>
<th>
<a href="https://www.w3.org/2016/05/browser-testing-tools-charter.html">Rechartered</a>
</th>
<td>
<i>19 May 2016</i>
</td>
<td>
<i>31 March 2017</i>
</td>
<td>
<i>No changes in scope or deliverables.</i>
</td>
</tr>
<tr>
<th>
Charter Extension
</th>
<td>
<i>1 April 2017</i>
</td>
<td>
<i>30 September 2017</i>
</td>
<td>
<i>No changes in scope or deliverables.</i>
</td>
</tr>
<tr>
<th>
Charter Extension
</th>
<td>
<i>1 October 2017</i>
</td>
<td>
<i>30 June 2018</i>
</td>
<td>
<i>No changes in scope or deliverables.</i>
</td>
</tr>
<tr>
<th>
<a href="https://www.w3.org/2018/12/browser-testing-tools.html">Rechartered</a>
</th>
<td>
<i>1 December 2018</i>
</td>
<td>
<i>31 December 2020</i>
</td>
<td>
<i>No changes in scope or deliverables.</i>
</td>
</tr>
<tr>
<th>
Charter Extension
</th>
<td>
<i>1 January 2021</i>
</td>
<td>
<i>31 March 2021</i>
</td>
<td>
<i>No changes in scope or deliverables.</i>
</td>
</tr>
<tr>
<th>
Rechartered
</th>
<td>
<i>TDB</i>
</td>
<td>
<i>TDB + 2 years</i>
</td>
<td>
<i>WebDriver Bidirectional Protocol deliverable added. New Patent Policy 2020.</i>
</td>
</tr>
</tbody>
</table>
</section>
</section>
</main>
<hr>
<footer>
<address>
<a href="mailto:mike@w3.org">Michael Smith</a>
</address>
<p class="copyright">
<a href="https://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> ©
2021
<a href="https://www.w3.org/"><abbr title="World Wide Web Consortium">W3C</abbr></a><sup>®</sup>
(
<a href="https://www.csail.mit.edu/"><abbr title="Massachusetts Institute of Technology">MIT</abbr></a>,
<a href="https://www.ercim.eu/"><abbr title="European Research Consortium for Informatics and Mathematics">ERCIM</abbr></a>,
<a href="https://www.keio.ac.jp/">Keio</a>,
<a href="https://ev.buaa.edu.cn/">Beihang</a>
), All Rights Reserved.
<abbr title="World Wide Web Consortium">W3C</abbr> <a href="https://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>, <a href="https://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a> and <a href="https://www.w3.org/Consortium/Legal/copyright-documents">document use</a> rules apply.
</p>
<hr>
<p><a href="https://github.com/w3c/charter-drafts">Yes, it's on GitHub!</a>.</p>
</footer>
</body>
</html>