> For the complete documentation index, see [llms.txt](https://www.opal-rt.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.opal-rt.com/docs/hypersim/automation-api-and-scripting/automate-using-testview/navigate-the-interface.md).

# Navigate the Interface

## Main window overview

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-9a69fcb0e16d3495a9c19b902958390bff955cfa%2Fimage%20(1209).png?alt=media" alt=""><figcaption></figcaption></figure>

<table data-search="false"><thead><tr><th width="267.63641357421875">Area</th><th>Description</th></tr></thead><tbody><tr><td><strong>1. Project Explorer</strong></td><td>Displays all studies and tests in the current project.</td></tr><tr><td><strong>2. Palette / Runner / View Tabs</strong></td><td>Used to create tests (Palette), execute tests (Runner), and control how results are shown (View).</td></tr><tr><td><strong>3. Script Window</strong></td><td>Allows editing the test sequence.</td></tr><tr><td><strong>4. Parameters Window</strong></td><td>Displays command parameters for the selected step in the script.</td></tr><tr><td><strong>5. Stdout Console</strong></td><td>Shows verbose test execution output.</td></tr><tr><td><strong>6. Memory Monitor</strong></td><td>Indicates Java heap memory usage during execution.</td></tr><tr><td><strong>7. Context Menu &#x26; Shortcuts</strong></td><td>Provides quick access to common TestView actions.</td></tr></tbody></table>

## Menu bar

### File menu

* **New Project…** — Create a new `.prj` project or open an existing one if the name matches.
* **New Study…** — Create a study to organize multiple tests.
* **New Test…** — Create a test anywhere in the project or inside a study.
* **Open Project…** — Open an existing `.prj` TestView project.
* **Refresh Project** — Refresh Project Explorer after external file changes.
* **Save / Save All** — Save one or all modified tests.
* **Exit** — Close TestView.

### Edit menu

* **Copy / Paste / Cut /** **Delete** **command** — Copy, duplicate, or remove script commands.\
  Commands are always pasted under the currently selected script line.

### Tools menu

* **HYPERSIM Connection...** — Choose which HYPERSIM instance and which open model TestView connects to. TestView interacts with a **copy** of the model stored in its project folder. Any changes made to the original model **after** the copy is created will **not** appear in TestView.
* **Import HYPERSIM Network...** — Not supported. Do not use.
* **Import HYPERSIM I/O Sensors...** — Imports `.sig` files (same function as HYPERSIM Settings → Sensors).
* **Signals Manager...** — Select which signals TestView will acquire during processing. Each selected signal is acquired during every test iteration; selecting hundreds of signals can significantly increase total test time.
* **Import Macro...** — Import `.csh` macro scripts into the project.

## Right‑click menus

### Project Explorer right‑click options

{% columns %}
{% column width="41.66666666666667%" %}

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-cea2b48608a72770f5d212741c122602a4fab6f1%2Fimage%20(1210).png?alt=media" alt=""><figcaption></figcaption></figure>
{% endcolumn %}

{% column width="58.33333333333333%" %}

* **New Study...** — Create a study to organize multiple tests.
* **New Test…** — Create a test anywhere in the project or inside a study.
* **Open / Close**
* **Unlock** — Required to overwrite test results.
* **Copy / Paste** — Duplicate tests or studies.
* **Add to Batch** — Add tests or studies to the batch execution list.
* **Zip** — Creates a ZIP archive of a selected test or study.
* **Import Test** — Import `.tst` tests from a directory.
* **Delete / Rename**
* **Validate** — No supported. Do not use.
* **Save**
* **Open Pre‑settings / Post‑settings** — Comments automatically shown at the start or end of a test.
* **Open note book...** — Notes not displayed during test execution.
* **Open output log...** — Records everything printed in the Stdout console during a test, allowing you to review past executions even after the console is cleared.
* **Properties...**
  {% endcolumn %}
  {% endcolumns %}

### Script window right‑click options

{% columns %}
{% column width="33.33333333333333%" %}

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-fa988b1032c4319149f0922554b3b1d598d8a86b%2Fimage%20(1211).png?alt=media" alt=""><figcaption></figcaption></figure>
{% endcolumn %}

{% column width="66.66666666666667%" %}

* **Properties...**
* **Expand Tree...**
* **Copy / Paste / Cut**
* **Move Left / Right** — Change command hierarchy level
* **Move Up / Down** — Reorder commands within the same level
  {% endcolumn %}
  {% endcolumns %}

## Palette, Runner, and View tabs

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-8d0366c4697a4ada5f3ceeff84f0598e63c2acdf%2Fimage%20(1213).png?alt=media" alt=""><figcaption></figcaption></figure>

{% tabs %}
{% tab title="Palette" %}
Contains all commands available for building a test script. Commands are inserted below the selected script line.

**Note:**\
Only **HYPERSIM Test** can be placed at the root of a script.
{% endtab %}

{% tab title="Runner" %}
The **Runner** tab controls how TestView executes tests and in what order. It also allows you to configure and run **batch tests**.

* **Unlock test auto:**\
  When enabled, a test is unlocked automatically before execution.\
  When disabled, if the test is locked, TestView prompts you to confirm unlocking before it can run.
* **Save test auto:**\
  When enabled, the test is saved automatically before execution.\
  When disabled, if unsaved changes are detected, TestView prompts you to confirm saving.
* **Current test only / All tests open / Use Batch Test:** Choose how the **Play** button executes tests:\
  When **Current test only** is selected, only the test currently displayed in the Script window runs.\
  When **All tests open** is selected, all open tests run sequentially, starting with the one in the active Script window.\
  When **Use Batch Test** is selected, the list of tests added to the **Batch Test List** runs, even if they are not open. To add a test to the batch list, right‑click its name in the Project Explorer and select **Add \[Test] to batch**. When Batch Test mode is selected, a **Viewer Options** dialog appears with display settings from the View tab. Because batch runs typically execute many tests, it is recommended to disable visualization (e.g., ScopeView displays) to avoid pausing execution. If the batch test list is empty, the Play button does nothing.
  {% endtab %}

{% tab title="View" %}
Controls how results appear during execution.

* **Processing / Post‑Processing / Table display**\
  Overrides Processing command’s display settings.\
  Useful to avoid ScopeView windows pausing batch runs.
* **Pre‑Settings / Post‑Settings display**\
  Shows or hides user‑defined comments before/after tests.
  {% endtab %}
  {% endtabs %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://www.opal-rt.com/docs/hypersim/automation-api-and-scripting/automate-using-testview/navigate-the-interface.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
