Running scripts from DevOps Test UI

You can run scripts from HCL DevOps Test UI (Test UI) so that all of your recorded actions are played back. The recorded actions include the actions that you performed to start and stop an application, add verification points, and any other actions that you performed while using the application.

Before you begin

You must have completed the following tasks:

Procedure

  1. Configure your application under test by setting the appropriate Java™ environment or web browser to run the application.
  2. Run the script in any of the following ways:
    • Open the script from the Functional Test Projects view, and then click Run Functional Test Script Run Functional Test Script button in the Test UI toolbar.
    • Right-click the script in the Functional Test Projects view, and then click Run.
    • Click the script in the Functional Test Projects view, and then click Script > Run.

    The Select Log dialog is displayed.

  3. Retain the default log name or enter a log name for your script.
  4. Optional: Select the following checkboxes, if they are not selected:
    1. Don't show this wizard again: Select the checkbox to prevent the Script Launch wizard from starting each time you run the test script.
    2. Enable handling of unexpected windows: Select the checkbox to enable the unexpected window handling feature for the test script.
    3. Enable script find if scoring find fails: Select the checkbox to enable the dynamic find feature for the test script.
    Note: You can enable any of these features in the Windows > Preferences page for all the scripts. The corresponding checkbox is automatically selected in the Select Log dialog for all the subsequent functional tests. You can clear a checkbox in the Select Log dialog, if you do not want to enable the feature for the script that you are running.
  5. Click Next.
    The Specify Playback Options dialog is displayed.
  6. Optional: Perform the following tasks in the Specify Playback Options dialog:
    1. Enter or select the command-line arguments in the Run arguments field to pass to the script.
      The most recently used command-line arguments appear in the list.
    2. Select a number or select Iterate Until Done in the Dataset Iteration Count field to specify the number of times the test script can run during the playback.
    3. Select the Perform playback in interactive mode checkbox to dynamically resolve the common runtime situations.
    4. Select the Enable Response Time Breakdown checkbox to generate performance metrics for the application under test.
  7. Click Finish to run the test script.

Results

Test UI is minimized, and the playback monitor is started. While the script plays back all of your recorded actions, the corresponding messages are displayed in the playback monitor.

What to do next

After the test playback is completed, you can view the results of the playback in the test log that is displayed in a separate browser window.

Note: If the playback monitor does not start, or the test log does not open in Test UI, you can click Windows > Preferences > Functional Test > Playback, and then check the settings on the Monitor page and Logging page, respectively.