4fcd3ae25f
* reinstate * start server manually * routing tests too * skip more * sleep more and fail if not 200 * use e2etest for content/ too * automatically start server for jest * does this work? * feedbacked * rename things * getting it to work * add dev dependency * install the right version * don't need to start that * fix package lock * update readme about it * feedbacked
104 lines
2.9 KiB
Markdown
104 lines
2.9 KiB
Markdown
## Tests
|
|
|
|
It's not strictly necessary to run tests locally while developing: You can
|
|
always open a pull request and rely on the CI service to run tests for you,
|
|
but sometimes it's helpful to run tests locally before pushing your changes to
|
|
GitHub.
|
|
|
|
Test are written using [jest](https://ghub.io/jest), a framework maintained
|
|
by Facebook and used by many teams at GitHub. Jest is convenient in that it
|
|
provides everything: a test runner, an assertion library, code coverage analysis,
|
|
custom reporters for different types of test output, etc.
|
|
|
|
### Install optional dependencies
|
|
|
|
We typically rely on CI to run our tests, so we consider some large test-only
|
|
dependencies **optional** (for example, puppeteer). In order to run the tests locally you'll
|
|
need to make sure optional dependencies are installed by running:
|
|
|
|
```sh
|
|
npm ci --include=optional
|
|
```
|
|
|
|
If you run into the error "Could not find expected browser (chrome) locally" you may need to manually install the expected chromium version with:
|
|
```
|
|
node node_modules/puppeteer/install.js
|
|
```
|
|
|
|
### Running all the tests
|
|
|
|
Once you've followed the development instructions above, you can run the entire
|
|
test suite locally:
|
|
|
|
```sh
|
|
script/test # or `npm test`
|
|
```
|
|
|
|
### Watching all the tests
|
|
|
|
You can also run a script that will continually watch for changes and
|
|
re-run the tests any time a change is made. This command will notify you
|
|
when tests change to and from a passing or failing state, and will also print
|
|
out a test coverage report, so you can see what files are in need of tests.
|
|
|
|
```sh
|
|
npm run test-watch
|
|
```
|
|
|
|
### Running individual tests
|
|
|
|
You can run specific tests in one of these two ways:
|
|
|
|
```sh
|
|
# The TEST_NAME can be a filename, partial filename, or path to a file or directory
|
|
npm test -- <TEST_NAME>
|
|
|
|
NODE_OPTIONS=--experimental-vm-modules npx jest tests/unit
|
|
```
|
|
|
|
### Failed Local Tests
|
|
|
|
If the tests fail locally with an error like this:
|
|
|
|
`Could not find a production build in the '/Users/username/repos/docs-internal/.next' directory.`
|
|
|
|
You may need to run this before every test run:
|
|
|
|
```sh
|
|
npx next build
|
|
```
|
|
|
|
### Linting
|
|
|
|
To validate all your JavaScript code (and auto-format some easily reparable mistakes),
|
|
run the linter:
|
|
|
|
```sh
|
|
npm run lint
|
|
```
|
|
|
|
### Keeping the server running
|
|
|
|
When you run `jest` tests, that depend on making real HTTP requests
|
|
to `localhost:4000`, the `jest` tests have a hook that starts the
|
|
server before running all/any tests, and stops the server when it's done.
|
|
|
|
You can disable that, which might make it easier when debugging tests
|
|
since the server won't need to start and stop every time you run tests.
|
|
|
|
In one terminal type:
|
|
|
|
```sh
|
|
NODE_ENV=test PORT=4000 node server.mjs
|
|
```
|
|
|
|
and then, in another terminal type:
|
|
|
|
```sh
|
|
START_JEST_SERVER=false jest tests/rendering/foo/bar.js
|
|
```
|
|
|
|
Or whatever the testing command you use. Note the `START_JEST_SERVER=false`
|
|
environment variable that needs to be set or else, `jest` will try to start
|
|
a server on `:4000` too.
|