Differences

This shows you the differences between two versions of the page.

--- first_steps_in_tast [2024/10/09 11:55]
montse [Doble Autentication in the TAST web application]
+++ first_steps_in_tast [2025/01/09 10:41] (current)
montse [Prerequisites for installing TAST]
@@ Line 15: / Line 15: @@
   - 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”.\\ \\
   -  Add exception on the “Edit Site List” option on the “Security” tab:\\ a. Click on “edit site list”.\\ \\ {{ :es:imagen4.jpg?350 |}}\\ b. Click on “Add”\\ {{ :es:imagen5.jpg?350 |}}\\ c. Add locations:\\ \\ For SIPSA environment:\\ https://app.cloud1.testautomationsystemtool.com/\\ \\
-  - Download the TAST drivers folder from this link:\\ [[https://testautomationsystemtool.com/cliente/sw/AppTast.zip]]\\ \\ and unzip it to "C:"\\ \\ {{ :es:imagen6.jpg?350 |}}\\ \\
+  - Download the TAST drivers folder from this link:\\ [[https://testautomationsystemtool.com/cliente/sw/AppTast.zip]]\\ \\ Unzip it with in your user folder (%USERHOME%), usually you will find it in C:\Users\<userid>\\ \\ {{ :imagen7.png?350 |}}\\ \\
@@ Line 236: / Line 236: @@
 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.
+To logout, the user needs to click on its user (upper right) and then will see the Logout button.\\ \\
@@ Line 253: / Line 253: @@
   * 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.
-{{ :doble_autenticacion3en.png?250| }}
+{{ :doble_autenticacion3en.png?250 |}}
-  * If the user has problems accessing or has lost access to the Authentication Application and codes, contact Technical Support at tast.support@sipsa.net
+  * If the user has problems accessing or has lost access to the Authentication Application and codes, contact Technical Support at [[tast.support@sipsa.net]]\\ \\
@@ Line 267: / Line 267: @@
 ==== Download ====
-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.
+To be able to use this tool, the first step is to download it from TAST, through the //User// option that appears in the upper right part of the application.
-{{:client_eng_1.png?nolink&800|}}\\ \\
+{{ :iconosen.png?direct&100 |}}\\
-The HTML client can be downloaded in two formats: exe and jar.\\
+{{ :descargasen.png?direct&600 |}}\\ \\
-{{:client_eng_2.png?nolink&800|}}
-  * 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).
+We have the TAST Client in its two versions. We can download the version we need and move it to the appropriate folder for the application:\\ \\
-  * 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//.
+{{ :downloadsclients.png?direct&600 |}}\\
+  * **Client Exe Version**
+      * Client app .exe version. Running the exe will generate the jar of the current version of the client application and two jars of hosts, jagacy3270 and tn5250.
+  * **Client Version Jar**
+         * Client app .jar version. By downloading this jar, we can access the current version of the Client application.\\ \\
 ==== Functionality ====
@@ Line 339: / Line 343: @@
     * logs of the execution,
     * screenshots (if previously indicated),
-    * other files (if proceeds) result of the execution: excel, scripts,...
+    * other files (if proceeds) result of the execution: excel, scripts,...\\ \\
+=====Filters in Tast Client=====
+{{ :es:filtros_en_el_cliente_tast.png?direct&400 |}}
+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.
+{{:es:filtros_en_el_cliente_tast2.png?50|}}Clicking on the Filter table button applies the filters entered in the fields to the table\\
+{{:es:filtros_en_el_cliente_tast3.png?50|}}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.
+====Test case name====
+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”)
+====Last execution date====
+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)
+====Status====
+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:
+{{ :es:filtros_en_el_cliente_tastayuda1.png?direct&400 |}}
+By clicking on this button, a screen appears with all the necessary help to filter the elements using these three fields.
+{{ :es:filtros_en_el_cliente_tastayuda2.png?direct&400 |}}

TAST DokuWiki

User Tools

Site Tools

Differences

Page Tools