Executing a Test Run




Pre-execution criteria

To successfully execute a Test Run there are a number of criteria that MUST be met, they are:  

Starting execution

Before execution is due to start the User should check that the criteria outlined above have been met for the Test Run.

Once the criteria above have been met to start execution: Whichever method is chosen to start execution the Confirm execution star dialog box will be displayed:
If the User chooses "Yes" then TETware professional will then perform all the necessary checks to ensure that the Test Run can be executed.

If any of the criteria outlined above are NOT met by the configuration for the Test Run then an appropriate dialog box will be displayed indicating the error (The dialog boxes are not displayed here due to the large number possible).

If all the criteria outlined above ARE met by the configuration for the Test Run then TETware professional will then generate all the configuration files that are needed by TETware professional to perform a successful execution. The following files will be generated if TETware professional Lite is being used: It should be noted that for the same Test Run conditions the files are overwritten when the Test Run is re-executed.

Once all the relevant files have been generated the command line to use to execute TETware professional is built. Once the command line has been built TETware professional is started with the environment set to the values indicated in the Test Run configuration.

Please note: a 2 second delay has been added to allow time for the Operating System to deliver the captured output to TETware professional, it was found during testing that there are times when TETware professional can finish execution but the Operating System did not deliver the captured output before TETware professional had detected that it had finished. The consequence of this was that TETware professional indicated that it had finished but no output was displayed. To circumvent this a delay was added to enable the output from TETware professional to be captured correctly.

Notes on the executing Test Run

The "executing" icon will be displayed for the duration that the Test Run is executing.

Whilst the Test Run is executing the menu items relating to Test Run execution will be disabled, that is "Execute Test Run", "Quick Re-run" and "Advanced Re-run". However, the "Stop Test Run" menu item will be enabled.

If  TETware professional starts execution correctly then the "Execution Output" node icon will change from to . This indicates that TETware professional  is executing.

Whilst executing a Test Run TETware professional will capture the standard output and standard error streams and display them in the "Execution Output" and "Error Output" text areas on the right-hand side of TETware professional respectively.

Once the Test Run has started executing control will be returned to the User so that they can allow the Test Run to execute and continue with the management of other Test Runs etc.

 

Journal file name

Once the output has been captured TETware professional will  determine what the Journal file name is for this Test Run execution. The Journal file name once captured will be used to display the contents of the Journal file in the Journal text area, please click here for more information on browsing Journal files. When Test Run execution has finished the Journal file name will be written to the Journal file name in the Report panel so it can then be used for the generation of a Report for the Test Run. For more information on the Report panel click here. The Journal file name will also be written to a the Journal file name in the Database Extract Tool, for more information on writing Journal file parameters to a database please click here.

 

Stopping a Test Run

Stopping Test Runs whilst they are executing is NOT recommended since it can undesirable effects on the system. For more information on stopping Test Runs please click here.

 

When a Test Run stops?

When a Test Run has finished execution then the "Execution Output" node icon will change from to . This indicates that the Test Run has finished executing. 

Re-executing a Test Run

A Test Run can be re-executed at any time (providing that it is not currently executing). Please note however that the criteria detailed above still hold, i.e. if you change any configuration for the Test Run then it will be used for the re-execution not the previous configuration.

It is also possible to perform partial re-execution of Test Runs, please see the links below for more details:



© The Open Group 1995-2002