When a Test Run is created or opened this node is also opened.
The following table gives a description of each tree node and it's use within the Test Run.
For options available by Right Clicking on these Nodes please click
here.
Tree Node Name | Tree Node Icon | Description |
---|---|---|
Test Run Open | ![]() | This node is the base node for all the subsequent nodes relating to an individual Test Run, from this node you are able to add a scenario file, save and remove the Test Run. It is the starting point for the Test Run. |
Test Run Closed | ![]() | This node is the closed version of the Test Run Open node described above, when this icon is displayed it indicates that the Test Run has been hidden in the tree. |
Configuration | ![]() | This node is starting point for the configuration for the Test Run. Attached to this node is a "local system" node which holds the local systems configuration. Remote systems are also attached to this node. If you click on this node then the Main configuration screen for the Test Run will be displayed. |
Local System | ![]() | This node represents the local systems configuration. The local system is the system on which TETware professional will be invoked. Clicking on this node displays the local systems configuration screens. |
Remote System | ![]() | This node represents a remote system that will be used in the Test Run. This node is optional and is only required when TETware professional is being used in distributed mode, i.e. for remote or distributed testing. Clicking on this node displays the configuration screens for that remote system. |
Execution Output Started | ![]() | As the name suggests this node, when shown, indicates that the Test Run is currently executing. The output can be viewed in the Execution screens. The Execution screens can be seen by clicking on this node. This icon will be displayed for as long as the Test Run is executing. |
Execution Output Stopped | ![]() | As the name suggests this node, when shown, indicates that the Test Run is NOT currently executing. Clicking on this icon will display the Execution screens. |
Journal | ![]() | Clicking on this icon will take you to the Journal file display screen. If you have performed a Test Run for which there was a Journal file generated then it will be displayed here. Right-clicking on this node allows you to Browse the file system for a Journal file. Note: you cannot open a Journal file which is greater than 2MB in size. |
Reporting | ![]() | Clicking on this node will take you to the Reporting screen where you can specify a report to be generated using a Journal file or configure the database extract tool and specify the Journal file parameters to be passed to the database . |
Scenario File | ![]() | This node represents the Scenario file. If valid scenarios
exist within the Scenario file then these are displayed as scenario nodes below this
node. Clicking on this node will display the Scenario file in the Scenario file display
window. Right-clicking on this node allows you to refresh the scenario file (basically
re-read the Scenario file if it has changed), include and exclude all the scenarios,
remove the Scenario file, and display the path to the Scenario file.
If no scenario file is included then right clicking on this node allows you to add an existing scenario file, or create a new scenario file. |
Scenario Included | ![]() | This node represents a scenario from the Scenario file that should be Included when the Test Run is executed. Single clicking on the scenario node will toggle it's included/ excluded status. |
Scenario Excluded | ![]() | This node represents a scenario from the Scenario file that should be Excluded when the Test Run is executed. Single clicking on the scenario node will toggle it's included/ excluded status. |