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

feat(misc): move ci options to configuration #14215

Merged

Conversation

DaSchTour
Copy link
Contributor

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

@vercel
Copy link

vercel bot commented Jan 7, 2023

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

Name Status Preview Comments Updated
nx-dev ✅ Ready (Inspect) Visit Preview 💬 Add your feedback Jan 21, 2023 at 1:39PM (UTC)

@nx-cloud
Copy link

nx-cloud bot commented Jan 7, 2023

☁️ Nx Cloud Report

CI is running/has finished running commands for commit face364. 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


⌛ The following target is in progress

🟥 Failed Commands
nx affected --target=test --base=c6adec7f9d9536eee9507cdc38a0209af69dce02 --head=45230d241cc92af553cadd1ff73c843913a8afba --parallel=1
✅ Successfully ran 12 targets

Sent with 💌 from NxCloud.

@AgentEnder
Copy link
Member

Changes make sense, can you fix the failing tests? CC @barbados-clemens, you see any issue w/ this?

@barbados-clemens
Copy link
Contributor

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.

@DaSchTour
Copy link
Contributor Author

I haven't worked with jest snapshots before. That's why the test were failing. Should be updated now.

@barbados-clemens
Copy link
Contributor

Looks like angular, nest, node, and nx-plugin are still out of date. they might be using .toEqual() instead of snapshots which is why they didn't get updated.

Using the Nx Cloud link you can see the failing tests. Or you can just run nx affected --target=test to see them locally.

make test task depend less on jest specific options and use configuration instead to be more
inclusive

ISSUES CLOSED: nrwl#12045
@github-actions
Copy link

github-actions bot commented Mar 8, 2023

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 8, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

nx-cloud workflow doesn't work with karma test
3 participants