Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Docs: Add an example for the e2e tests snapshot update #41999

Merged
merged 2 commits into from Jun 28, 2022
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
5 changes: 4 additions & 1 deletion docs/contributors/code/testing-overview.md
Expand Up @@ -305,6 +305,9 @@ However, if the change was intentional, follow these steps to update the snapsho
```sh
# --testPathPattern is optional but will be much faster by only running matching tests
npm run test-unit -- --updateSnapshot --testPathPattern path/to/tests

# Update snapshot for e2e tests
npm run test-e2e -- --updateSnapshot --testPathPattern path/to/e2e-tests
```

1. Review the diff and ensure the changes are expected and intentional.
Expand Down Expand Up @@ -606,7 +609,7 @@ To ensure that the editor stays performant as we add features, we monitor the im

Performance tests are end-to-end tests running the editor and capturing these measures. Make sure you have an e2e testing environment ready.

To set up the e2e testing environment, checkout the Gutenberg repository and switch to the branch that you would like to test. Run the following command to prepare the environment.
To set up the e2e testing environment, checkout the Gutenberg repository and switch to the branch that you would like to test. Run the following command to prepare the environment.

```
nvm use && npm install
Expand Down