You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+14-14
Original file line number
Diff line number
Diff line change
@@ -9,23 +9,23 @@
9
9
*Thank you*:kissing_heart: to all of you interested in helping. These are Mocha's immediate needs:
10
10
11
11
1. Increase test coverage on Node.js and browser
12
-
- Increase integration coverage for all reporters
13
-
-`html` reporter must be tested in browser
14
-
-~~Basic console reporters (*not*`nyan`, `landing`, etc.) must be tested in **both** browser and Node.js contexts; PhantomJS can consume all console reporters~~
15
-
-~~Filesystem-based reporters must be tested in Node.js context~~
16
-
-**UPDATE - May 24 2017**: Thanks to [community contributions](https://github.com/mochajs/mocha/blob/master/CHANGELOG.md#mag-coverage), the coverage on most reporters has increased dramatically! The `html` reporter is still in [dire need of coverage](https://coveralls.io/builds/11674428/source?filename=lib%2Freporters%2Fhtml.js).
17
-
- Increase coverage against all interfaces (`exports` in particular). Ideally this becomes a "matrix" where we repeat sets of integration tests across all interfaces.
18
-
- Refactor non-Node.js-specific tests to allow them to run in a browser context. Node.js-specific tests include those which *require* the CLI or filesystem. Most everything else is fair game.
12
+
- Increase integration coverage for all reporters
13
+
-`html` reporter must be tested in browser
14
+
-~~Basic console reporters (*not*`nyan`, `landing`, etc.) must be tested in **both** browser and Node.js contexts; PhantomJS can consume all console reporters~~
15
+
-~~Filesystem-based reporters must be tested in Node.js context~~
16
+
-**UPDATE - May 24 2017**: Thanks to [community contributions](https://github.com/mochajs/mocha/blob/master/CHANGELOG.md#mag-coverage), the coverage on most reporters has increased dramatically! The `html` reporter is still in [dire need of coverage](https://coveralls.io/builds/11674428/source?filename=lib%2Freporters%2Fhtml.js).
17
+
- Increase coverage against all interfaces (`exports` in particular). Ideally this becomes a "matrix" where we repeat sets of integration tests across all interfaces.
18
+
- Refactor non-Node.js-specific tests to allow them to run in a browser context. Node.js-specific tests include those which *require* the CLI or filesystem. Most everything else is fair game.
19
19
2. Review current open pull requests
20
-
- We need individuals familiar with Mocha's codebase. Got questions? Ask them in [our chat room](https://gitter.im/mochajs/mocha).
21
-
- Pull requests **must** have supporting tests. The only exceptions are pure cosmetic or non-functional changes.
22
-
- Pull request contributors must sign [the CLA](https://cla.js.foundation/mochajs/mocha).
20
+
- We need individuals familiar with Mocha's codebase. Got questions? Ask them in [our chat room](https://gitter.im/mochajs/mocha).
21
+
- Pull requests **must** have supporting tests. The only exceptions are pure cosmetic or non-functional changes.
22
+
- Pull request contributors must sign [the CLA](https://cla.js.foundation/mochajs/mocha).
23
23
3. Close old, inactive issues and pull requests
24
-
-~~A bot should do this. We need a bot. Got a bot?~~ We now use GitHub's own [probot-stale](https://www.npmjs.com/package/probot-stale).
24
+
-~~A bot should do this. We need a bot. Got a bot?~~ We now use GitHub's own [probot-stale](https://www.npmjs.com/package/probot-stale).
25
25
4. Triage issues
26
-
- If we run into "critical" bugs, they need fixing.
27
-
- "Critical" means Mocha is broken w/o workarounds for a *large percentage* of users
28
-
- Otherwise: respond to issues, close new dupe issues, confirm bugs, ask for more info, etc.
26
+
- If we run into "critical" bugs, they need fixing.
27
+
- "Critical" means Mocha is broken w/o workarounds for a *large percentage* of users
28
+
- Otherwise: respond to issues, close new dupe issues, confirm bugs, ask for more info, etc.
29
29
30
30
Once we gain ground on the above items, we can work together formalize our contribution guidelines and governance. For further info & ideas, please see our [projects](https://github.com/mochajs/mocha/projects/).
0 commit comments