Setups

Overview of how to create and manage Setups in Typhoon Test Hub.

A Setup is a group of HIL devices and DUTs which will be used "as a unit" to run certain tests. Setups are an important component of Typhoon Test Hub. The Job Execution Queue is based on Setup availability. During Job creation you can inform which Setup should be used by that execution.

When writing the Job Execution command, environment variables TTH_SETUP_HIL_IP and TTH_SETUP_HIL_SN will be automatically available for the script. When a Job is connected to a setup, these two variables will be automatically populated based on the HIL devices that are part of the chosen setup.
  • IP addresses of those HIL devices will populate the TTH_SETUP_HIL_IP variable, where the IP addresses will be separated using a comma, for example: 192.168.0.80, 192.168.0.81, 192.168.0.82
  • Serial numbers of those HIL devices will populate the TTH_SETUP_HIL_SN variable, where the serial numbers will be separated using a comma, for example: 00604-11-12345, 00402-07-12345.

If your Setup is connected to the network, it can also be visible and available for manual testing. It is possible to reserve a Setup (item under the Action column), so the Hub will not start any executions with that Setup.

Figure 1. Setups table

The Setups table shows the following information:

  1. Status: Offline and Available
  2. Name
  3. Number of HILs
  4. Number of DUTs

From this table, you can also click the button, which will reserve the setup for only the current user. Once reserved, it will show icon next to status like this:

By clicking the button, a user with a reserved Setup can make it available again for other users.

Note: By clicking on the button, columns of the table can be customized - hidden or shown depending on the preference. Columns of the table can be reordered by using drag and drop in the table header. When positioning cursor in between two columns, cursor for column resizing will show and enable change of the column's width. All changes made to the table will be automatically preserved.

Setup details

Figure 2. Setup details

In the Details section (Figure 2), you can find the following tabs:

  1. Overview tab: Here you can update the name and description of setups, as well as see the number of HILs and DUTs that are in the setup.
  2. Configuration tab: This tab is shown in Figure 3. Here you can configure a Setup by selecting the available HILs and DUTs that you want and dragging and dropping them from the Available devices (left) into the Chosen setup (right). Alternatively, you can use the and arrows to move a single element from one list to the other, or use the and arrows to move all elements from one list to the other. You can also manipulate the order of elements in the list by selecting an element and using the and arrows to move it up/down one place, or the and arrows to move the element to the top/bottom of its list.
  3. Changes history tab tab: Contains setup's history of changes.
  4. Figure 4 tab: Shows setup's utilization.
Figure 3. Setup Configuration tab
Note: A HIL or DUT can only be part of one setup at a time. It is possible to reserve Setups to be used for manual tests. Typhoon Test Hub avoids starting Executions with Setups marked for manual tests, but keeps them in the Queue until the Setup becomes available.
Figure 4. Setup utilization

In the details section, you can delete a setup by clicking on the button.

Create setup

A new setup can be added by clicking on the button. This opens a form where you can define the properties of your new setup (Figure 5).

Figure 5. Create new setup form

To finish creating a setup, you must:

  1. Give it a name which will be used to refer to it throughout Typhoon Test Hub. Each name must be unique.
  2. Write a description for the setup.
Note: In order to save a form, all input fields must be valid. Required fields are signed with *.

Changes history tab

Changes history for the selected Setup is visible from this tab (Figure 6).

Figure 6. Setup changes history

All snapshots (events) will be exported to JSON format and automatically downloaded by clicking on the button. By selecting each line in the table, single snapshot will be shown enabling preview of the made changes and allowing user to perform comparison between the selected snapshot and and any chosen snapshot.

Figure 7. Selected snapshot preiew

Single snapshot (event) can be exported as JSON and downloaded by clicking on the button. Snapshots can be compared through UI or as JSON, with JSON option having more clearly displayed differences between the two snapshots using Monaco editor.

Figure 8. Snapshot comparisson through UI
Figure 9. Snapshot comparisson through JSON