TAST (Test Automation System Tool) is a tool for automating the testing. It is based on UML diagrams. It has a user-based system, where every user has a role and, depending on this role, can perform different actions.

The first screen seen when accessing to the tool is the one here below, where the user needs to log in, in order to get into its personal TAST view. This login can be done with the same credentials than for accessing Windows (i.e. LDAP number N000000 or XI000000 and password).

After clicking the “Sign in” button, the first webpage seen is the DASHBOARD of the tool, where the user can see the main useful information about the tool and its last use.

For switching between the different functionalities of the application, the user can use the menu at the left side of the screen. This menu can be presented in two ways (collapsed or expanded). In this menu, can be selected the following options:

• Dashboard.
• Settings.
• Customize.
  • Domains & Projects.
  • Projects & Users.
• User Roles.
• Infrastructure.
• Modeling.
  • UML Diagram.
  • Data Management.
• Running.
  • TS Management.
  • Planning.
• Results.

The button 'Modeling' will drive the user to the page that allows to create UML diagrams.

To logout, the user needs to click on its user (upper right) and then will see the Logout button.

The function of the TAST HTML client is to execute the test cases and test sets.

To be able to use this tool, the first step is to download it from TAST, through the Client option that appears in the upper right part of the application.

The HTML client can be downloaded in two formats: exe and jar.

• With the '.exe' option, a 'tast.zip' file is downloaded, which we will have to save somewhere in our computer, and extract the file that appears inside the zip.

This file has the format: tast_vn.nn.nn, where 'n.nn.nn' is the version of the HTML client (example: tast_v1.20.23.exe).

• With the '.jar' option, a 'tast.jar' file is downloaded, which we will have to save in the path:

C:\AppTast

To be able to use tast.jar we must also have in the path C:\AppTast the file TAST.cmd.

The first screen seen when accessing to the HTML Client is the one here below, where the user needs to log in, in order to get into its personal TAST HTML Client. This login can be done with the same credentials than for accessing TAST (i.e. LDAP number N000000 or XI000000 and password).

After clicking the “Login” button, some of the following messages will appear, depending on whether the HTML client version is the last or not:

1- HTML client version is the last:

• Clicking 'Yes' button, all the executions (pending or executed) of the logged-in user will appear.

• Clicking 'No' button, all executions of the HTML client will be deleted, appearing the empty table.

2- HTML client version is not the last:

• Clicking 'Accept' button, the window of section 1 will appear, with all the executions (pending or executed) of the logged-in user will appear.

At the top of the main window of the HTML client, will appear three options:

• Refresh.
• Delete.
• Schedule.

The HTML client window is updated with all the executions that are in that moment, adding:

• all the Test Cases launched from the 'Launch Validation' option of Modeling.
• all the Test Sets launched from the 'Execute Test Set' option of Test Set Management.

Allows to eliminate the selected test cases and test sets.

When clicking on this option, the planned executions that are ready to be executed will appear in the window (according to Planning functionality).

In this table appears the following information:

• Test Set name: the name of the Test Case or Test Set.
• Exc.Time(ms): run time of the Test Case or Test Set, expressed in milliseconds.
• Step: it is used to indicate the step in which you want to stop the execution. (Debug Mode).
• Debug: the two icons are only enabled when Debug Mode is used.
• Action: there are three possible actions:
  • execute the test case / test set: can be used when the iconappears.
  • stop the test case / test set: once the execution has started (the iconappears), it can be stopped by clicking on that icon. When the execution stops, will be shown the following window:
    
    
  • restart the test case / test set: once the execution has been paused (appears in Status), it can be restarted by clicking on theicon.
• Status: shows the status of the executions. It can contain the values:
  

the test case / test set has not yet been executed.
the test case / test set has been executed and finished ok.
the test case / test set has been executed and finished ko.
the test case / test set has been pause.
when the evidences can not be uploaded and recorded correctly in the NAS where the results are stored.

• Logs: clicking on this option, the client opens an explorer window with the path where are the following files:
  • logs of the execution,
  • screenshots (if previously indicated),
  • other files (if proceeds) result of the execution: excel, scripts,…