Documentation Home Page ◇ HYPERSIM Home Page
Pour la documentation en FRANÇAIS, utilisez l'outil de traduction de votre navigateur Chrome, Edge ou Safari. Voir un exemple.
TestView | GUI Walkthrough
- 1 Main Window
- 2 Main Window Menus
- 2.1 File Menu
- 2.1.1 New Project…
- 2.1.2 New Study…
- 2.1.3 New Test…
- 2.2 Open Project…
- 2.2.1 Refresh Project
- 2.3 Save
- 2.4 Edit Menu
- 2.4.1 Copy [Selected Command]
- 2.4.2 Paste [Selected Command]
- 2.4.3 Cut [Selected Command]
- 2.1 File Menu
- 3 Tools Menu
- 3.1.1 HYPERSIM Connection
- 3.1.2 Import HYPERSIM Network
- 3.1.3 Import HYPERSIM I/O Sensors
- 3.1.4 Signals Manager
- 3.1.5 Import Macro
- 3.2 Help Menu
- 3.2.1 About
- 3.2.2 User Manual
- 3.3 Right-Click Menu in Project Explorer
- 3.4 Import test
- 3.4.1 Delete [Name of Test/Study]
- 3.4.2 Rename [Name of Test]
- 3.4.3 Validate [Name of Test/study/Project]
- 3.4.4 Save [Name of Test/Study/Project]
- 3.4.5 Open Test Pre-settings
- 3.4.6 Open Test Post-Settings
- 3.4.7 Open Note Book
- 3.4.8 Open Output Log
- 3.4.9 Properties…
- 3.4.10 Create a PDF Database
- 3.4.11 Create a CSV Database
- 3.5 Right-Click Menu in Script Window
- 3.5.1 Properties…
- 3.5.2 Expand tree…
- 3.5.3 Copy [Name of Selected Command]
- 3.5.4 Paste [Name of Copied Command]
- 3.5.5 Cut [Name of Selected Command]
- 3.5.6 Move Left [Name of Selected Command]
- 3.5.7 Move Right [Name of Selected Command]
- 3.5.8 Move Up [Name of Selected Command]
- 3.5.9 Move Down [Name of Selected Command]
- 4 Palette, Runner and View Tabs
- 4.1 Palette Tab
- 4.2 Runner Tab
- 4.2.1 Options
- 4.2.2 Batch Test List
- 4.3 View Tab
Main Window
You can open TestView from HYPERSIM, by using the TestView button in the HYPERSIM tab.
(1) Project explorer | All the studies and tests in the current project are accessed from this panel. |
(2) Palette, Runner and View tabs | To edit, run, and view results. |
(3) Script window | To edit the test. The commands can be moved using the arrows near the number 6. |
(4) Parameters window | All command parameters are displayed in this window. |
(5) Stdout (Console window) | The test verbose results are displayed in this window. |
(6) Memory monitoring | Real-time monitoring of the Java Heap Memory from the program. |
(7) Contextual menu and shortcuts | To access the different options from TestView. |
Main Window Menus
NOTE that names given to these various elements may NOT have spaces in them.
File Menu | File Menu |
|---|---|
New Project… | Displays the window below. Enter a name for the project. Clicking Apply closes the project that was already open if any, and opens a new project. If the user types the name of a project that already exists, it opens the existing one instead of creating a new one. New Project Dialog Box |
New Study… | Displays the window below. Enter a name for the study. A study can regroup several tests and can even regroup studies. Clicking Apply adds a new study to the current project. New Study Dialog Box |
New Test… | Displays the windows below. Enter a name for the test. A test may or may not be created inside a study. It depends on the selected option in the Project Explorer window. Clicking Apply to the first dialog box will open the second dialog box. The description field is optional. |
Open Project… | Displays the window below. Select a TestView project file (.prj). Only .prj files are supported in TestView. Selecting a .prj file closes the opened project and opens the selected project. Open Project Dialog Box |
Refresh Project | Click to refresh the Project explorer window. If a study file is deleted, for instance, the change is not visible in the Project explorer without clicking on Refresh Project. |
Save | Click to save the currently selected test. This option is grayed out if no test is selected or open. |
Save All | Click to save all the tests modified in the project. This option is grayed out if no test is open. |
This option is currently not supported. Do not use. | |
Exit | Clicking this option closes the program. |
Edit Menu
Copy [Selected Command] | Use this option to copy a command that is currently selected in the opened script in the Script window. This option will be grayed out if no command is selected. The text in parenthesis will change depending on the command selected in the script. |
|---|---|
Paste [Selected Command] | Use this option to paste commands in the Script window that is currently open. It will be pasted directly underneath the selected command in the Script window. This option will be grayed out if no command is copied or cut. The text in parenthesis will change depending on the command copied or cut in the script. |
Cut [Selected Command] | Use this option to copy and delete a command from the currently opened test in the Script window. This option will be grayed out if no command is selected. T he text in parenthesis will change depending on the command selected in the script. |
Tools Menu
HYPERSIM Connection
Displays the window below. The connection option is to select which HYPERSIM to connect to. If there are two opened instances of HYPERSIM for example, the user would have the choice to select between HYPERSIM [1] and HYPERSIM [2]. In the Edition section, the current design dropdown menu has a list of all the models that are open in one HYPERSIM instance. It is recommended to only have one model open while working with TestView.
Note: It is important to keep in mind that TestView does not interact directly with the original model. When a script is executed for the first time, TestView will make a copy of the model in the TestView project directory and interact with this model onwards.
If the copy is detected in the project folder, it will not re-copy the original model again. Therefore, if some modifications are made to the original model after the copy was made, the modifications will not be applied to the copy, thus they will not be affecting the test sequence.
Import HYPERSIM Network
Deprecated functionality. Import a .sch model (legacy Linux user interface) to the project.
Import HYPERSIM I/O Sensors
Import signal sensors (.sig) to the project. It has the same functionality as importing the sensors from the HYPERSIM Settings command.
Signals Manager
Display the window below. The Signals Key Manager is similar to the Sensors form in HYPERSIM.
However, considerations must be taken here for the performance of the test sequence as every signal selected will be acquired with every test, based on the parameters entered in the Processing command.
One more signal might not be perceptible, but hundreds more signals could mean several more seconds at each test, which would lead to a few more hours to run an entire test sequence with thousands of tests.