Local System Monitor Pane (Test/Business Component Settings Dialog Box / Application Area - Additional Settings Pane)

Relevant for: GUI tests and components

This pane enables you to activate system monitoring, and define the system counters you want to track during a run session. These counters enable you to monitor the resources used by your application.

Any Local System Monitor data that is captured during a run session is displayed in the run results.

Access the Local System Monitor pane

Do one of the following to access the Local System Monitor pane:

Tests

With a test, action, or business component in focus, select File > Settings > Local System Monitor node.

Application areas

Open the application area and select Additional Settings > Local System Monitor in the sidebar.

User interface elements

The Local System Monitor pane includes the following UI elements:

UI Element

Description

Enable local system monitoring every: __ seconds

The frequency in seconds, by which the system counters for this application will be checked.

Use the up and down arrows or enter a value in the edit box to change the number of seconds.

Minimum value: One second.

Application to monitor

The application whose system counters you want to monitor.

For more details, see Define your local system monitoring settings.

System Counter / Limit

The system counter you want to track for the selected application, and the upper limit of the counter selected in the System Counter column.

For more details, see Define your local system monitoring settings.

Removes the system counter definition from your test or application area.

Description

The description of the counter selected in the System Counter column, as provided by the performance console application.

Back to top

Define your local system monitoring settings

Define the applications and counters you want to monitor as follows:

  1. In the Local System Monitor pane, select the Enable local system monitoring checkbox, and define the monitoring frequency.

  2. Define the application to monitor in any of the following ways:

    Enter the name manually

    Enter the name of the application's executable file (without file extension) in the edit box.

    Select from the dropdown

    Click the down arrow in the edit box to display any of the following:

    • Applications previously run in OpenText Functional Testing.

    • Currently running applications.

    • Applications currently specified in the Windows Applications tab of the Record and Run Settings dialog box.

    • Applications currently specified in the Additional Settings pane in an Application Area.

    For more details, see:

    Browse

    Click the browse button and browse to the application's executable file.

    Make sure that your application is currently running. Then click the pointing hand and point to the application on your desktop.

    Note: Sometimes a process is used only as a launcher that creates another process that provides the application functionality. Make sure to select the executable file that actually provides the application functionality.

  3. In the table below, define your system counters and limits. Click inside a cell and select a counter from the dropdown list.

    The Limit value is optional.

    • If the selected counter exceeds this value during the run session, the run fails.
    • If you do not supply a value, the counter is tracked and the results are displayed in the run results.

    System counters supported for monitoring include the process counters that are accessible through the performance console (select Start > Run > and then enter Perform). For more details, see the performance console's documentation.

    Tip: Click the expand button when displayed to show more counters.

Back to top

Multiple application instances

If more than one process with the same name runs during a run session, and you monitor a counter for that process, the counter is sampled from the application instance that contains at least one test object from the test or component. If multiple applications meet this criterion, only one application is monitored.

For example, this may occur if you select to monitor a counter for iexplorer.exe process, and you have multiple Internet Explorer browser windows open during the run session.

If you have multiple instances of the same application running, OpenText Functional Testing monitors the instance that was opened first.

Back to top

Local system monitoring for Business Process Testing

When working in a component, the Local System Monitor pane is read-only. Define the Local System Monitor settings in the application area associated with your component.

When running a business process test, local system monitoring uses the settings defined for the application area associated with the first component in the test. If another component that runs later in the business process test is associated with a different application area, local system monitor settings from that application area are ignored.

Back to top

Local system monitoring and mobile tests

If you are running a Mobile test and have Device Metrics selected on the Mobile tab of the Record and Run Settings dialog box, the Device Metrics settings override any settings in the Local System Monitor pane.

For more details, see Define Mobile Record and Run Settings.

Back to top

See also: