-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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: Refine Node API & Improve test [WIP] #1395
Conversation
- feat: Add getFragment、context、usePlugin - fix: cannot debug test cases at a child process
@shigma Feel free to continue to improve tests into this branch, meanwhile, we need to do following things:
|
<div class="highlighted"> </div> | ||
<br> | ||
</div>export default function () { // .. } | ||
</div> | ||
`; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@shigma Note that this snap shouldn't be removed, I guess this case need to be updated.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed at #1398
console.log(`running node with args: ${args.join(' ')}`) | ||
await execa('node', args, { | ||
await execa('jest', args, { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The jest runner is running under a child process, this change will cause the fail of debug
since --inspect-brk
is a node-level flag.
To make debug work, we need ensure that Parent and child process won't share the same inspecting port;
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We can merge this feature request first, and I believe this is not the real reason why Windows can't run test. Looking forward to your PR later. 😉
Summary
yarn test
since it's running as a child process.What kind of change does this PR introduce? (check at least one)
If changing the UI of default theme, please provide the before/after screenshot:
Does this PR introduce a breaking change? (check one)
If yes, please describe the impact and migration path for existing applications:
The PR fulfills these requirements:
fix #xxx[,#xxx]
, where "xxx" is the issue number)You have tested in the following browsers: (Providing a detailed version will be better.)
If adding a new feature, the PR's description includes:
To avoid wasting your time, it's best to open a feature request issue first and wait for approval before working on it.
Other information: