Open gkamperis opened 1 year ago
Is it possible that it works with nx:affected test --parallel -- --browsers="CustomChromeBrowser"
?
This issue has been automatically marked as stale because it hasn't had any recent activity. It will be closed in 14 days if no further activity occurs. If we missed this issue please reply to keep it active. Thanks for being a part of the Nx community! 🙏
bump
Current Behavior
We have a large monorepo with a mix of jest and karma test suits.
For karma we have
customLaunchers
After migrating to
v16.3.2
the commandnx:affected test --parallel --browsers="CustomChromeBrowser"
on some projects is attempting to launchChrome
instead ofCustomChromeBrowser
As we are running in CI and Chrome is not allowed (only headless is) this leads to failure.Anyhow, the issue is that the
--browsers
flag is lost in the process.A total assumption on my part: I suspect that at some point some logic removes it because maybe it is not valid for
jest
? or because of some sort of failure it picks up the default?Anyway, this is an assumption of course but there is definitely a bug somewhere where flags are not propagated correctly when you have mixed targets that do not all support the same flags/arguments.
Expected Behavior
I expect all flags to be passed to all calls of the
test
targetThis was working fine at least in
v15.1.1
GitHub Repo
No response
Steps to Reproduce
It is not easy for me to provide a reproduction repo.
Nx Report
Failure Logs
No response
Operating System
Additional Information
No response