Modifying the recorded data in a monitoring script

You can modify the user actions and the input values that are recorded in a monitoring script and that persist as the default values in the script. When you run the updated monitoring script, the new input values and user actions are used as reference data to monitor the application.

About this task

If you apply user actions and enter values during the recording of a monitoring script while an application is running, all the completed user actions and the input values that you enter in the Monitoring view are automatically saved in a .test_mnt file. To modify the default data and re-run the monitoring script with the new reference data, follow this procedure:

Procedure

  1. Apply one of the following procedures to open and modify the recorded script:
    • To edit the .test_mnt file in the script editor:
      • Double-click the .test_mnt file in the Project explorer view .
      • Click the Data tab in the graph and modify the values directly in the different table cells.

        The table displays in green the meta-commands with the user actions (read, write, frequency, and so on) and the input values. Other values are output values that are sent by the application when the monitoring script is run. You can modify all the input values and user actions. Then, when you re-run the updated script, the output data that is received from the application are compared with the reference data.

      • Select the appropriate cells in a row or column and right-click to display the options in the contextual menu to add, remove, or cut rows or columns in the table.
      • Click Save .
    • To edit the .test_mnt file a the text editor:
    Note:
    • The variable values that are not checked are identified by the NaN item (Not a Number) in the report because they are not requested during the monitoring process. You can monitor the following data types for the basic data: numeric, integer, or float data. For he collection of data elements, you can monitor these data types: array, structure, and union. However, the output format of the data is always numeric.
    • The report gives the time when the variable values were read or written in the application.
    • You can extract these values for testing or re-running. To extract these values, remove the lines that are prefixed with the hash sign (#) and exported a file in the .csv format.
    The .test_mnt file is displayed in your project in the Project Explorer and saved in your workspace. You can create multiple scripts. They are named with the following format: ProjectName_ScriptNumber.test_mnt where the ScriptNumber value is automatically increased.
  2. Click the updated .test_mnt file in the Project explorer view to refresh the Monitoring view or click to browse to your file and click OK.
    The Monitoring and the Project explorer views are refreshed.
  3. Click Settings in the Monitoring view to set parameters to use while the test script runs:
    • Quick start, Start application , and Stop application options are the default selected options in the settings. When selected, they automatically start and stop the application when you click Run. The Quick start option is used to start the application from the first write user action in the test. Only write user actions and new frequencies are played. Other actions are ignored.
    • The Start application option is a default selected value. When selected, it automatically runs the application. You can decide to run a script or re-run a script when it is complete but you don't want to stop the application? In this case, deselect the Start application option.
    • The Disable report generation option is not selected. By default, a report is automatically generated when the monitoring script run is complete. Click this option, if you want no report when the monitoring script is played.
  4. Click Run in the Monitoring view.
    The application runs in the background. Each time you run a script file, a ProjectName.replay.Date.rtx file is created and displayed. It contains the graph with the updated data and variables. You can delete the replay.rtx files but you cannot edit them.

What to do next

When the script is complete, an HTML report is created. You can open and examine all the events and information that the script run generated.