In addition to enabling script debugging in Internet Explorer and nice add-ons for Firefox like Firebug and Web Developer, you can also use the Debug Div component in the attached example protocol.
It adds an area to your report for messages generated by JavaScript. To generate messages, use the function
printDebug()
with a string argument in your script. The component also provides a link to clear the current messages.
Once your script is working well, you can either
1. Remove the component from your protocol, *also taking care to remove all calls to printDebug() in your code*, or
2. Set the HideDebugDiv parameter on the component to True.
Right-click on the Debug Div and choose "Save As" to save it to your xmldb for later re-use.
It adds an area to your report for messages generated by JavaScript. To generate messages, use the function
printDebug()
with a string argument in your script. The component also provides a link to clear the current messages.
Once your script is working well, you can either
1. Remove the component from your protocol, *also taking care to remove all calls to printDebug() in your code*, or
2. Set the HideDebugDiv parameter on the component to True.
Right-click on the Debug Div and choose "Save As" to save it to your xmldb for later re-use.