| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
1 parent 434af03 commit 8c4c84f
1 file changed
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -32,6 +32,7 @@ back in to the CTC. | |||
| 32 | 32 | * [Intl](#intl) | |
| 33 | 33 | * [HTTP](#http) | |
| 34 | 34 | * [Documentation](#documentation) | |
| 35 | + * [Testing](#testing) | ||
| 35 | 36 | ||
| 36 | 37 | #### Process: | |
| 37 | 38 | ||
@@ -287,6 +288,18 @@ Its responsibilities are: | |||
| 287 | 288 | * Creating and operating a process for documentation review that produces | |
| 288 | 289 | quality documentation and avoids impeding the progress of Core work. | |
| 289 | 290 | ||
| 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 | + | ||
| 290 | 303 | ## Starting a WG | |
| 291 | 304 | ||
| 292 | 305 | A Working Group is established by first defining a charter that can be | |
| Back | FazBrowse Home | New Git URL |
0 commit comments