feat(nx-plugin): thread jest options through nx-plugin:e2e executor

[chiubaka]

Current Behavior

nx-plugin:e2e executor doesn't expose any of the underlying jest CLI options, making it hard to use, and in some cases incorrect.

E.g. Since E2E tests for generators in plugins operate on a single expected E2E directory (tmp/nx-e2e/proj), there is some potential for conflict due to Jest's default parallelism in tests if two tests are messing with that directory simultaneously using functions like ensureNxProject. I'd like to be able to try the --runInBand option to see if it resolves what I'm seeing, but am unable to do so because the e2e executor hides this arguments.

Unsure if this is technically a feature or a bug fix as a result.

Expected Behavior

I should be able to pass any typical jest CLI option down to the e2e executor and expect it to pass them down to the underlying jest process.

Related Issue(s)

I didn't open an issue for this. Just decided to directly PR.

[nx-cloud-staging]

☁️ Nx Cloud Report

CI is running/has finished running commands for commit a50da83. As they complete they will appear below. Click to see the status, the terminal output, and the build insights.

📂 See all runs for this branch

---

✅ Successfully ran 12 targets

• nx affected --target=e2e --base=eae3d4562529920babb1fd7b3daee8354992572f --head=a50da830838542a9bee15c71f5af2d320e23663d --exclude=e2e-storybook,e2e-storybook-angular,e2e-react-native,e2e-detox --parallel=1
• nx affected --target=build --base=eae3d4562529920babb1fd7b3daee8354992572f --head=a50da830838542a9bee15c71f5af2d320e23663d --parallel=3
• nx affected --target=lint --base=eae3d4562529920babb1fd7b3daee8354992572f --head=a50da830838542a9bee15c71f5af2d320e23663d --parallel=3
• nx affected --target=test --base=eae3d4562529920babb1fd7b3daee8354992572f --head=a50da830838542a9bee15c71f5af2d320e23663d --parallel=1
• nx-cloud record -- yarn nx workspace-lint
• nx-cloud record -- yarn documentation
• nx build typedoc-theme
• nx-cloud record -- yarn depcheck
• nx-cloud record -- yarn check-lock-files
• nx-cloud record -- yarn check-commit
• nx-cloud record -- yarn nx format:check --base=eae3d4562529920babb1fd7b3daee8354992572f --head=a50da830838542a9bee15c71f5af2d320e23663d
• nx-cloud record -- yarn check-imports

---

Sent with 💌 from NxCloud.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated
nx-dev	✅ Ready (Inspect)	Visit Preview	Aug 4, 2022 at 10:00AM (UTC)

[chiubaka]

FWIW, runInBand did solve my issue. Feels like this particular E2E harness could be a bit more robust wrt multiple test suites.

Might be overkill to allow every option for jest, but I think at a minimum, it would be nice to have --ci, -t, and --runInBand off the top of my head.

[github-actions]

This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request.