When you hover the cursor over a variable value, the variable code is displayed in a popup window.
This will generally only be necessary if automatic display of variables is disabled. To display the value of a variable at the breakpoint, enter the name of the variable and click the + to add it to the Inspector Panel. You can disable the automatic display of variables in General settings > Interactive options > Debug. The Inspector Panel displays all parameters and user-defined variables. When you replay the script, the Inspector Panel is displayed. A breakpoint is indicated by to the left of the step number.ĭuring replay, use breakpoints to inspect the values of variables in the Inspector Panel.ĭefine variables in an Evaluate JavaScript step. To insert a toggle breakpoint, right-click the desired step and select Toggle Breakpoint, or click to the left of the step number. They can be used to help debug your script. Log file that records various operations that were performed when running a script in load mode.īreakpoints instruct the script to stop running during a replay when in interactive mode. Log file that records various operations that were performed when running a script in interactive mode.Įxample: interactive_replay_TruClientBrowser.txt
TruClient log files are stored in the TruClient script folder: Select Output Pane > - Interactive Replay. You can view details of your script's replay in the VuGen Output Pane. These log files may be useful when debugging a TruClient script.
TruClient maintains log files that record various operations that were performed when running a script in interactive and load mode. Repeat this procedure after each step to continue the step by step replay. To run the script step by step, select the down arrow from the replay button in the browser and select Replay step by step. You can run your script step by step to view the replay more slowly and in a controlled manner. Hover the mouse over these icons to view descriptions of the errors. If any steps failed during replay, they are marked with an error
#Script debugger lite how to#
With that approach, you can also pin-point version-specific problems.Īlso you can look at How to troubleshoot script errors in Internet Explorer article by Microsoft.View replay errors in the TruClient Development window
#Script debugger lite install#
Install IE Tester, which emulates various IE instances (versions), and use its built-in Debug Bar.Install Debug Bar, which provides an extended feature-set to the built-in developer tools.It is a proxy that enables tools to debug and diagnose IE using the Chrome remote debug protocol. If you don't have access to files you can still use Firebug Lite with this bookmarklet: javascript:(function(F,i,r,e,b,u,g,L,I,T,E))(document,'createElement','setAttribute','getElementsByTagName','FirebugLite','4','firebug-lite.js','releases/lite/latest/skin/xp/sprite.png','','#startOpened') If you have access to files, you can stick this tag to the page you are trying to debug and it will open Firebug: To get the Internet Explorer toolbar to stay visible, click Alt, click View, point to Toolbars and check Menu bar, and then click Lock the toolbars.
0 kommentar(er)
