miel.truyen/nx
1
0
Fork 0
Code Issues Pull Requests Actions 5 Packages Projects Releases Wiki Activity

docs(misc): add info about running E2E in CI-like env to CONTRIBUTING (#13730)

Browse Source
This commit is contained in:
Miroslav Jonaš 2022-12-09 12:49:07 +01:00 committed by GitHub
parent ecf9a80bae
commit 2ff6b11f46
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 9 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
CONTRIBUTING.md
View File

@ -119,7 +119,7 @@ nx test jest
### Running E2E Tests ### Running E2E Tests
**Use Node 14 and NPM 6. E2E tests won't work on Node 15 and NPM 7.** **Use Node 16 and NPM 8. E2E tests won't work on Node 15 and NPM 7.**
To make sure your changes do not break any E2E tests, run: To make sure your changes do not break any E2E tests, run:
@ -133,6 +133,14 @@ Running E2E tests can take some time, so it is often useful to run a single test
nx e2e e2e-cli -t versions # I often add qqqq to my test name so I can use -t qqqq nx e2e e2e-cli -t versions # I often add qqqq to my test name so I can use -t qqqq
``` ```
Sometimes tests pass locally but they fail on the CI. To reproduce the CI environment and be able to debug the issue, run:
```bash
NX_VERBOSE_LOGGING=true CI=true PACKAGE_MANAGER=pnpm yarn nx e2e e2e-cli --t="should do something is this test"
```
The above command sets verbose logging (this exposes stack traces and underlying errors), sets the defaults to be CI-like and sets Pnpm as the selected package manager.
### Developing on Windows ### Developing on Windows
To build Nx on Windows, you need to use WSL. To build Nx on Windows, you need to use WSL.