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
Explanation:
I have a Fitnesse script that executes javascript routine verantwoordelijkheden() that I wrote.
I find that I can use the javascript debugger from DevTools to step through that code,
provided that that javascript code is loaded from a separate file,
so that that file can be inspected from DevTools > Sources.
And after it is loaded, I have the Fitnesse script execute a pause statement,
allowing me to open file verantwoordelijkheden.js from DevTools,
and setting a breakpoint.
Then I continue from the pause statement, and have a command
|show|execute script|verantwoordelijkheden()|
that then hits the breakpoint.
This works very nice, except that I get the ScriptTimeoutException after 30 seconds, or sometimes somewhat longer.
The text was updated successfully, but these errors were encountered:
How can I specify a high script timeout , so that I can step through the javascript without getting
I can't figure out how to do that using $localconfig in
|start managed driver for|edge|with profile|$localconfig|
Explanation:
I have a Fitnesse script that executes javascript routine
verantwoordelijkheden()
that I wrote.I find that I can use the javascript debugger from DevTools to step through that code,
provided that that javascript code is loaded from a separate file,
so that that file can be inspected from DevTools > Sources.
So the JSCODE imports that file:
And after it is loaded, I have the Fitnesse script execute a pause statement,
allowing me to open file verantwoordelijkheden.js from DevTools,
and setting a breakpoint.
Then I continue from the pause statement, and have a command
|show|execute script|verantwoordelijkheden()|
that then hits the breakpoint.
This works very nice, except that I get the ScriptTimeoutException after 30 seconds, or sometimes somewhat longer.
The text was updated successfully, but these errors were encountered: