Skip to content

Commit d4a1fc7

Browse files
TrottMyles Borins
authored and
Myles Borins
committed
doc: add Testing WG
Add the proposed Testing WG. WORKING_GROUPS.md indicates that opening a pull request to that file is the way to request that a charter be ratified by the TC. So, that's what this is. The charter document is currently: https://github.com/nodejs/testing/blob/master/Charter.md PR-URL: #5461 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Alexis Campailla <[email protected]> Reviewed-By: Johan Bergström <[email protected]>
1 parent 1642078 commit d4a1fc7

File tree

1 file changed

+13
-0
lines changed

1 file changed

+13
-0
lines changed

WORKING_GROUPS.md

+13
Original file line numberDiff line numberDiff line change
@@ -32,6 +32,7 @@ back in to the CTC.
3232
* [Intl](#intl)
3333
* [HTTP](#http)
3434
* [Documentation](#documentation)
35+
* [Testing](#testing)
3536

3637
#### Process:
3738

@@ -287,6 +288,18 @@ Its responsibilities are:
287288
* Creating and operating a process for documentation review that produces
288289
quality documentation and avoids impeding the progress of Core work.
289290

291+
### [Testing](https://github.com/nodejs/testing)
292+
293+
The Node.js Testing Working Group's purpose is to extend and improve testing of
294+
the Node.js source code.
295+
296+
It's responsibilities are:
297+
298+
* Coordinating an overall strategy for improving testing.
299+
* Documenting guidelines around tests.
300+
* Working with the Build Working Group to improve continuous integration.
301+
* Improving tooling for testing.
302+
290303
## Starting a WG
291304

292305
A Working Group is established by first defining a charter that can be

0 commit comments

Comments
 (0)