Reorganize tests

* Rename test directory to test-tap

This makes way for new, self-hosted tests inside a test directory

* Rewrite TypeScript test to use tsd; move into test-d directory

* Simplify npm run scripts

* Invoke nyc ourselves

* Don't store tap and nyc configuration in package.json

* Remove stdout / stderr from reporter test fixtures

These've ended up being flaky on Windows all of a sudden.

.github/CONTRIBUTING.md

@@ -59,7 +59,7 @@ Try and avoid making breaking changes. Those take more time to ship. Instead mak
 
 Non-experimental features should be accompanied with tests and documentation.
 
-Don't include unrelated changes in your pull request. Make sure tests pass on your machine by running `npm test`. You can run specific test files as well using `npx tap --no-cov test/{file}.js`.
+Don't include unrelated changes in your pull request. Make sure tests pass on your machine by running `npm test`. You can run specific test files as well using `npx tap test-tap/{file}.js`.
 
 When you make a pull request please use a clear and descriptive title. Be specific about what's changed and why.
 

.taprc

@@ -0,0 +1,12 @@
+browser: false
+coverage: false
+esm: false
+files:
+  - "test-tap/*.js"
+  - "test-tap/reporters/*.js"
+  - "test-tap/integration/*.js"
+flow: false
+jobs: 2
+jsx: false
+timeout: 300
+ts: false

maintaining.md

@@ -7,7 +7,7 @@
 ## Testing
 
 * `npm test`: Lint the code and run the entire test suite with coverage.
-* `npx tap --no-cov test/fork.js --bail`: Run a specific test file and bail on the first failure (useful when hunting bugs).
+* `npx tap test-tap/fork.js --bail`: Run a specific test file and bail on the first failure (useful when hunting bugs).
 
 ## CI
 

nyc.config.js

@@ -0,0 +1,14 @@
+'use strict';
+
+module.exports = {
+	all: true,
+	exclude: [
+		'{coverage,media,test-d,test-tap}/**',
+		'*.config.js'
+	],
+	reporter: [
+		'html',
+		'lcov',
+		'text'
+	]
+};