first_steps_in_tast
Differences
This shows you the differences between two versions of the page.
|
first_steps_in_tast [2024/10/09 12:31] montse [Filters in Tast Client] |
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”.\\ \\ | - 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/\\ \\ | - 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 267: | Line 267: | ||
| ==== Download ==== | ==== 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 ==== | ==== Functionality ==== | ||
| Line 345: | Line 349: | ||
| =====Filters in Tast Client===== | =====Filters in Tast Client===== | ||
| - | {{ :en:filtros_en_el_cliente_tast1en.png?400 |}} | + | {{ :es:filtros_en_el_cliente_tast.png?direct&400 |}} |
| - | + | ||
| You can filter elements in the Client table using these 3 fields: | You can filter elements in the Client table using these 3 fields: | ||
| - | * Test set name, | + | * Test case name, |
| * Last execution date, | * Last execution date, | ||
| * Status | * Status | ||
| Line 362: | Line 366: | ||
| Filters will be applied to test cases, i.e. test case data belonging to a test set, and to validation test case data. | Filters will be applied to test cases, i.e. test case data belonging to a test set, and to validation test case data. | ||
| - | **Test set name**\\ \\ | + | ====Test case name==== |
| In the filter Test set name you can use: | In the filter Test set name you can use: | ||
| * Logical operators: OR, AND, NOT | * Logical operators: OR, AND, NOT | ||
| Line 376: | Line 380: | ||
| * Test* AND NOT xml* (testcases whose name contains the string “test” and does not contains the string “xml”) | * Test* AND NOT xml* (testcases whose name contains the string “test” and does not contains the string “xml”) | ||
| - | **Last execution date**\\ \\ | + | ====Last execution date==== |
| In the filter Last Exec. date you can use: | In the filter Last Exec. date you can use: | ||
| * Asterisk *: alone, indicates any date | * Asterisk *: alone, indicates any date | ||
| Line 393: | Line 397: | ||
| * 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) | * 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**\\ \\ | + | ====Status==== |
| In the filter Status you can use: | In the filter Status you can use: | ||
| * Logical operators: OR, AND, NOT | * Logical operators: OR, AND, NOT | ||
| * Keywords accepted: OK, KO, executed, notexec or notexecuted | * Keywords accepted: OK, KO, executed, notexec or notexecuted | ||
| - | * Upper or lower case: is the same | + | * Upper or lower case: is the same\\ |
| - | + | Some examples in this field:\\ | |
| - | Some examples in this field:\\ \\ | + | |
| * OK (testcases executed with result OK -green-) | * OK (testcases executed with result OK -green-) | ||
| * ok OR ko (testcases executed with result OK -green- or KO -red-) | * ok OR ko (testcases executed with result OK -green- or KO -red-) | ||
| Line 408: | Line 411: | ||
| - | And finally, important:\\ \\ | + | **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.\\ \\ |
| - | 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 |}} | ||
first_steps_in_tast.1728477095.txt.gz · Last modified: 2024/10/09 12:31 by montse
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Noncommercial-Share Alike 3.0 Unported
