-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
feat(misc): move ci options to configuration #14215
feat(misc): move ci options to configuration #14215
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Changes make sense, can you fix the failing tests? CC @barbados-clemens, you see any issue w/ this? |
Personally, I don't care much for code coverage being in the CI configuration, but I can be convinced since most people probably do end up use code coverage for CI and it helps reenforce the idea of nx configurations instead of just passing args all the time. |
6036a47
to
687f868
Compare
I haven't worked with jest snapshots before. That's why the test were failing. Should be updated now. |
Looks like angular, nest, node, and nx-plugin are still out of date. they might be using Using the Nx Cloud link you can see the failing tests. Or you can just run |
687f868
to
9f44b3a
Compare
9f44b3a
to
45230d2
Compare
make test task depend less on jest specific options and use configuration instead to be more inclusive ISSUES CLOSED: nrwl#12045
45230d2
to
face364
Compare
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. |
make test task depend less on jest specific options and use configuration instead to be more inclusive
ISSUES CLOSED: #12045
Current Behavior
Documentation suggests to add flags --ci and --code-coverage to tasks. This is specific for jest and might break with other tests.
Expected Behavior
To have a jest independent approach we might start with using configurations instead of specific flags.
Related Issue(s)
This would also allow preventing issues like #12045 and allow to run karma and jest test within one target.
Fixes #12045