-
Notifications
You must be signed in to change notification settings - Fork 53
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
Add test debugging support #109
base: master
Are you sure you want to change the base?
Conversation
When cli.js executed by Node.js running in debug mode, child processes are also running in debug mode with different port. It is possible to run cli.js in normal mode and debug only child processes using --debug option. It is possible to specify debug port after --debug option. Close qunitjs#108.
I should rewrite the cli with commander ... |
Hmm ... if we need to debug just one child why do we need all this. Arguments are passed to the child in any case. |
The only thing we need is to avoid that runner process gets this flag. |
The problem is not in passing debug argument to child process, but deeper - in fixing node way of spawning new processes when parent process is running in debug mode; also in ability to run child process in debug mode when parent process is running in normal mode. There are two parts that should be handled:
It is possible to simplify logic, avoid |
Guys, what is required to merge this PR? Or do you have any other suggestions on how to debug qunit tests? |
When cli.js executed by Node.js running in debug mode, child processes are also running in debug mode with different port.
It is possible to run cli.js in normal mode and debug only child processes using --debug option.
It is possible to specify debug port after --debug option.
Close #108.