Skip to main content

Welcome to the Cyara Knowledge Center

Search

Script/Error Script

Updated: tech writers Edited:

The Script and Error Script sections have an editor where you can enter your script.

You can enter a script that contains actions in the Macro Script language used by the Macro Scheduler.

For example, the following actions can be entered as a script:

  • To find a login window, you need to enter the username and password and then press enter.

For more information, refer to https://www.mjtnet.com/manual/index.html?welcome.htm

To enter a script, perform the following steps:

  1. Enter the Script text in Macro Script language.
  2. You can enter the Variables, Parameters, or Resources that were defined in the earlier sections. Select the relevant button to add these parameters.

    • Parameters: the user-provided parameters that can be entered at run time.

    • Variables: are exactly the same variables as those used in data validation.
    • Resources: give the ability to attach an image.
  3. To load a Macro Script from a file, use the Import Script option to browse your local computer.
  4. To execute and test run the script, click the Run button. A dialog box as shown is displayed:
  5. Select the List of Available Desktops. The drop-down list appears as per the desktops available.
    This list is refreshed based on the available Desktops; that is, when you run the Desktop Client. Refer to the Running Desktop Client topic for more information.
  6. Enter the Parameters specified in the Custom Activity parameter section. For example, if Username and Password were specified as parameters, they will appear as shown above.
  7. Enter the Variables specified in the Custom Activity variables section.
  8. Click Run. The script executes and displays results accordingly. A display panel with the screens recorded appears; the screen display is in a sequence of before and after executing the script.
  9. The Error Script section handles errors. That is, if the script did not execute successfully or is waiting for a screen pop, the error script will attempt to get the desktop state back to the way it was prior to the execution of the script. This is different from desktop functional tests because the desktop agent must be able to process the next call once it comes in.

    Refer to the Desktop Script Reference section for information on scripts.
Was this article helpful?
0 out of 0 found this helpful
Return to top

Related articles

Comments

0 comments

Please sign in to leave a comment.