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.

For being able to use TAST, it is needed to make a short configuration in the pc to let the program work as expected, be able to use the client, and avoid the security messages to come out every time that the tool is open. First of all, a set up for the client-permissions is needed.

The configuration is performed following these steps:

1. Check you have Java Runtime Environment (JRE) installed. To verify this, open a Windows command console and type: java -version. If you have the JRE installed, it will show which version you have, the version 1.8.0 is required. In case you don't have it installed, download it from the following link: https://www.java.com/en/download/. This step is completely needed.
   
   
2. Change the two environment variables: Run from the control panel → User Accounts → User accounts → Change my environment variables →
   
   
   a. If you have PATH, click on “edit” while selecting it. If you don’t have it, click on “new”.
   
   
   Add new values to variable PATH:
   
   C:\Program Files(x86)\Java\jre1.8.0_281
   C:\Program Files(x86)\Common Files\Oracle\Java\javapath
   C:\ProgramData\Oracle\Java\javapath
   
   (the numbers on the jre should correspond with your jre version).
   
   
   
3. Restart the PC.
   
   
4. Open java options following these steps:
   a. Click the Windows start button.
   b. Go to “control panel”.
   c. Go to “Programs”.
   d. Click on “Java”.
   
   
5. Add exception on the “Edit Site List” option on the “Security” tab:
   a. Click on “edit site list”.
   
   
   b. Click on “Add”
   
   c. Add locations:
   
   For SIPSA environment:
   https://app.cloud1.testautomationsystemtool.com/
   
   
6. Download the TAST drivers folder from this link:
   https://testautomationsystemtool.com/cliente/sw/AppTast.zip
   
   and unzip it to “C:“
   
   
   
   

To be able to automate HTML GUI pages, there are two ways to do it:

1. Through Selective Mapping.
2. F12 Browser.
   

TAST has created a proprietary tool, Selective Mapping, thanks to which, we can obtain the search values in a more efficient way. When using selective mapping, the best search options are suggested from top to bottom. We can search by name, type, xtpath, Css, Css attributes. The options available for the Selective Mapping functionality are:

• To pause or continue: <Spacebar>.
• To copy attribute content or search by: <Click + Control + C>
• To paste the content of the attribute or search by: <Click + Control + V>
• To view the html source: [v]
• To exit: [esc]

Here is how to install this tool.

1. In the browser, open the TAST tool
   
2. Add this page to Favorites Bar
   
   
   
   
   
3. Rename this favorite to ‘Selective Mapping’.
   
   
   
   
4. Make visible Selective Mapping in the browser's favourite bar:
   
   
   
   
5. Positioned in Selective Mapping, right mouse button, and select Properties:
   
   
   
6. Copy the following text in the URL:
   javascript:prefFile='';void(z=document.body.appendChild(document.createElement('script')));void(z.language='javascript');void(z.type='text/javascript');void(z.src='https://app.testautomationsystemtool.com/rest/selectivemapping');void(z.id='tast');
   In the case of having your own installation, you must replace <https://app.testautomationsystemtool.com/rest/selectivemapping>
   by <URL_TAST SERVER_ORGANIZATION>
   
   
   
   
7. After clicking on the Selective Mapping favorite, appears a window similar to the following:
   
   
   
   
8. The attributes will change depending on where the focus is in the web page.
   
   

First of all, we are going to create a very simple GUI diagram that will consist of a Google search of the official website of the newspaper EL PAÍS. Here is a link to the video with the explanation of this test case. https://vimeo.com/920514078/6d0a2f564f?share=copy

Next we are going to detail step by step how to create a similar diagram, which is going to consist of a Google search, of TAST SIPSA: Google will open → We will accept the Cookies message from our computer → We will include our Google search criteria → We will click on the button → We will click on the 1st option that appears.

Access UML Model/UML Diagram from the menu:

Select your domain and project

Creat a new diagram.

Fill in the fields to create the diagram with the name, description and location where we want to create it.

We start by drawing the diagram using the drawing tools found in the menu on the right of the screen. Press the + sign adn a drop down list will appear.

Select the second option: Object

The first Adapter we need is the User Adapter. This Adapter does not need Properties, but it is necessary, since all messages start from it.

Next select another Adapter, and in this case we need the GUI Adapter, which is the one that allows us to interact with all kinds of web pages, to navigate, extract data, validate, etc…

Accept the change of Adapter.

And we can now launch messages

This Adapter needs the folowing in the Properties tab, indicate the URL and the name of the Search engine, in this case Chrome.

The URL and the search engine are necessay. Other parameters are optional.

When then go to the Selective Mapping tab, click twice and open it. To the right of the image, a light gray drop-down will appear with some data, which will vary as we modify our search by pressing the [v] key and the help of a red marker

Thanks to this tool, we can obtain the search values, which must be included, by copying and pasting them in the next Object Mapping tab. We can search by: name, type, xtpath, Css attributes, according to what was marked in the SearchBy dropdown. We then paste it in the Element tab.

If we want to document a step, open the message documentation screen and give an explanation of this step. This will appear documented when downloading he evidence document.

When the finish giving all the properties to the messages, map the messages and if we want to we document them.

Once we have finished the whole process, we save the diagram and validate it.

If we cannot edit it or we want to open the diagram again, to make any changes, we have to go to the lock tab and unlock it.

This diagram is assigned a number by default.

We open Client, downloading the Exe version.

And this screen will appear, where we click on More information, never on Not Execute.

It will then take a few seconds for the Client to install.

Click on Accept

And it will appear:

We look for the test case, execute it, if there are no errors it will be marked in green.

The Test case is launched automatically and we can see how: Google is opened → Accept our PC's Cookies message → include our Google search criteria → click on the button → then click on the 1st option that appears.

Next to the green tab is a folder that contains all the It is found in our C directory:

Open it and we have all the steps performed, the predefined functions that we have needed for the messages and the result.

If we want to have this test case documented, we go to Results and click on the download tab.

It creates a Word document with the number of steps performed, the Result, the link to access the diagram and if we have documented the messages, it will also detail them.

To get the mapping of a message from the GUI adapter we can do it with the F12 key. In this case we are going to search for a type in Google, which is the field where we write the search we want to do in Google.

We open the page we want to diagram (URL of the GUI adapter). Press the F12 key on the keyboard and the console appears

We click on the arrow in the image that shows us the elements of the page that we want to select to inspect.

It is positioned on the element of which we want to obtain the mapping and it is clicked on it. The F12 screen will show the information of the element.

On the element, we double click on the field that we want to obtain so that it is selected. In our case, we are going to do the search by “name”. We copy the element (Ctrl + C).

We go back to mapping the message in our diagram. Where we select the search field (name) and the information copied from F12 in the element field.

If we want to search by Xpath or Css Selector, in the selected element in the console (F12), we right-click / copy / copy selector-copy Xpath. And it is pasted in the element field of the message mapping.

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 TAST web application allows to activate the double authentication (double layer of security) to enter the application.

As a requirement the user on a device (mobile phone, tablet, …) must have installed an authentication application such as, Google Authenticator application, or Twilio Authy Authenticator or other similar application.

The steps to follow are the following:

• The user logs into the TAST application with Username and Password.

• If the user has not configured the Authentication Application on his cell phone, a QR code and an alphanumeric code will appear on the screen for the user to scan the QR code or enter the alphanumeric code to perform the configuration.
  
  The Authentication Application generates a 6-digit code. This code is being renewed every few seconds (approximately 30 seconds). If the user does not enter it before that time, he/she must wait for another code to be generated and enter it in the TAST application.
  
  The user must then click on “Submit” for TAST to verify it. If it is correct, you will be logged in to TAST.
  
  

• If the user has already configured the Authentication Application on his/her cell phone (which will generate a 6-digit code), he/she should proceed as indicated in the previous point.

• If the user has problems accessing or has lost access to the Authentication Application and codes, contact Technical Support at tast.support@sipsa.net
  
  

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 (appearsin Status). It can be restarted by clicking on the icon.
    
    
• 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,…
    
    

You can filter elements in the Client table using these 3 fields:

• Test case name,
• Last execution date,
• Status

These filters can be used individually or together.

Clicking on the Filter table button applies the filters entered in the fields to the table
Clicking on the Clear filters button clears the filter fields and resets the table to its original state

Filters will be applied to test cases, i.e. test case data belonging to a test set, and to validation test case data.

In the filter Test set name you can use:

• Logical operators: OR, AND, NOT
• asterisk *: alone, or at the end of a string
• double quotes “: to delimit names containing blank spaces
• upper or lower case: is the same

Note: The test case data prefix “tcd_” or test case validation prefix “tcv_” are ignored in comparison.

Some examples in this field:

• “test excel” (testcases whose name is equal to “test excel”)
• bbdd* OR “test excel” (testcases whose name contains the string “bbdd” or is equal to “test excel”)
• NOT xml* (testcases whose name does not contain the string “xml”)
• Test* AND NOT xml* (testcases whose name contains the string “test” and does not contains the string “xml”)

In the filter Last Exec. date you can use:

• Asterisk *: alone, indicates any date
• Hyphen - : delimiter between 2 dates
• Date formats supported: “dd.MM.yyyy HH:mm” y “dd.MM.yyyy”
  

Some examples in this field:

• * (testcases executed at any date)
• 23.09.2024 08:40 (testcases whose last execution date/time is less than or equal to 23/09/2024 08:40)
• 23.09.2024 (testcases executed until 23/09/2024. In this case, since the time has not been indicated, the first hour of that day is taken by default, so the testcases whose last execution date/time is less than or equal to 23/09/2024 00:00 will be displayed).
• * - 23.09.2024 08:40 (testcases whose last execution date/time is less than or equal to 23/09/2024 08:40)
• * - 23.09.2024 (testcases executed until 23/09/2024. In this case, since the time has not been indicated, the first hour of that day is taken by default, so the testcases whose last execution date/time is less than or equal to * 23/09/2024 00:00 will be displayed).
• 23.09.2024 08:40 - * (testcases whose last execution date/time is greater than or equal to 23/09/2024 08:40)
• 23.09.2024 - * (testcases executed from 23/09/2024. In this case, since the time has not been indicated, the first hour of that day is taken by default, so the testcases whose last execution date/time is greater than or equal to 23/09/2024 00:00 will be displayed).
• 25.04.2024 17:18 - 23.09.2024 08:40 (testcases executed between that date range, that is, whose last execution date/time is greater than or equal to 25/04/2024 17:18 and less than or equal to 23/09/2024 08:40)
• 25.04.2024 - 23.09.2024 (testcases executed between that date range, in this case, since the time has not been indicated, the first hour of both days is taken by default, so the testcases whose last execution date/time is greater than or equal to 25/04/2024 00:00 and less than or equal to 23/09/2024 00:00)

In the filter Status you can use:

• Logical operators: OR, AND, NOT
• Keywords accepted: OK, KO, executed, notexec or notexecuted
• Upper or lower case: is the same
  

Some examples in this field:

• OK (testcases executed with result OK -green-)
• ok OR ko (testcases executed with result OK -green- or KO -red-)
• OK or KO or NotExec (testcases executed with result OK -green- or KO -red-, or those not yet executed)
• Executed (testcases executed, regardless of their green or red result)
• NOT ok (testcases without OK result. So this includes the testscases not yet executed as well as those with KO result)
• Executed and not ko (only the executed testcases with OK result. Note this example is similar to the first one).

IMPORTANT:

if one or more filters were applied to the table, when you try to run the test set, only the testcases that were filtered will be run.

For example, if you filtered the table with the field Status = “KO OR notexec”, when you click on the Run Test Set button, only the testcases with status KO and Not executed will be executed. That is, it only executes the testcases that appear in the filtered table.

Finally, we have a third help button:

By clicking on this button, a screen appears with all the necessary help to filter the elements using these three fields.