You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I discovered that the gulpfile spawns a subprocess, and in doing so drops the --inspect-brk flag.
I have found my temp workaround
// passed to the Node.js process itself and not to the script that it runs.
+ args.unshift("--inspect-brk")
args.unshift("--max-http-header-size=80000");
return spawn("node", args, options);
}
to be quite useful in allowing me to step through the automated user interactions and observe the expected behavior of the app. It would be nice if this was configurable on the command line.
Other PDF viewers
No response
The text was updated successfully, but these errors were encountered:
Is the feature relevant to the Firefox PDF Viewer?
No
Feature description
In attempting to connect a debugger to the integration tests
I discovered that the gulpfile spawns a subprocess, and in doing so drops the
--inspect-brk
flag.I have found my temp workaround
// passed to the Node.js process itself and not to the script that it runs. + args.unshift("--inspect-brk") args.unshift("--max-http-header-size=80000"); return spawn("node", args, options); }
to be quite useful in allowing me to step through the automated user interactions and observe the expected behavior of the app. It would be nice if this was configurable on the command line.
Other PDF viewers
No response
The text was updated successfully, but these errors were encountered: