Before enhancing a TruClient script, replay the script to synchronize the steps and debug any problems found.
Once the script has been recorded, you can replay it to see if there are any errors. During replay, you can see the recorded actions being replayed in the browser.
You must replay your script at least once so TruClient can perform some background tasks. You will probably replay more than once, while you debug the script.
Note: Close all Chrome development tools before replaying a script in TruClient Lite.
The following table lists the different options you can use during replay to make improvements and resolve issues in your TruClient scripts.
TruClient scripts are asynchronous which means steps do not have to wait for previous steps to complete.
Replay the script to synchronize the steps. During the first script replay, TruClient will try to automatically identify the End Event for each step
For details, see Synchronize script steps.
Replay the recorded script, and solve any problems found in the debugging process. For details on the different options to debug a TruClient script, see Debug TruClient scripts.
|Generate snapshots of failed steps||
You can use the snapshots generated during replay to debug scripts by viewing the snapshots of the failed steps.
For details, see TruClient snapshots.
|Resolve object identification issues||
If an error is discovered during replay, you can highlight the object that failed, and TruClient automatically recognizes the selected step. For details, see Resolve object identification issues in TruClient.
You can also use the Descriptor Editor to improve or control object identification in your TruClient scripts by adding or editing conditions. For details, see Descriptors to identify an object.