In the realm of software development and testing, efficiency and collaboration are essential for success. At SIPSA, we believe in adopting practices that optimize the testing process. That's why TAST is the test automation tool designed to simplify automation, with features that help maximize testing efficiency and coverage.

Below, we explain two of the many features of TAST that maximize the efficiency of software testing: the gates and repositories of TAST. These features offer flexible and powerful solutions that save you time while improving the quality and consistency of your tests.

What is a gate?

In TAST, test cases are defined with UML sequence diagrams that detail the step-by-step process. A gate is a diagram nested inside another diagram.

How to create a gate?

1. Publish the diagram: First, publish the diagram you want to use as a Gate at the project or domain level.
2. Select the gate: In TAST, select the option to create a new Gate.
3. Draw the gate: Insert the Gate into the main diagram.
4. Configure properties: Define the properties of the Gate, including the corresponding domain and project.

Example: Gate URL

To illustrate how a gate works, let's consider a test case that involves automatically opening 100 different websites and capturing a screenshot of each to verify that they load correctly.

• Gate GUI: We use a diagram that captures the screenshot of a webpage and convert it into a gate.
• URL Loop: We insert this Gate into a loop that accesses an Excel file where the 100 URLs are listed, opening them sequentially and capturing the screenshot of each.

This gate can be reused in any other diagram that needs to capture a webpage screenshot, ensuring that any changes made to the Gate are reflected in all diagrams that contain it.

Benefits of using gates

• Efficiency: Gates allow for the reuse of existing test cases, saving time and effort by avoiding duplicated work.
• Simplicity: They simplify tests, making them more visual and easier to follow.
• Modularity: Gates promote modularity in test case creation, adapting easily to iterative development deliveries.

What is a repository in TAST?

A repository in TAST is a feature that allows centralized storage of variables and XPaths. TAST repositories are YML or TXT files that facilitate the management and reuse of data in automated tests.

How to create a repository in TAST?

1. Manage repositories: In the Model menu, select "Manage Repositories". Click + to create a new repository, defining its name and the corresponding domain/project/folder.
2. Write content: Write the content of the repository, such as XPath, CSS Selectors, IDs, etc.
3. Link to the diagram: Open the test case (diagram) and link the steps that use the data from the repository.

In TAST, repositories can also be cloned to make the initial setup process easier.

Example: SAP Repository

To illustrate the use of a repository, let's consider an automated test case for the SAP web application. This test case involves: logging in, creating a project for a new client, creating work packages, assigning resources, issuing an invoice, and changing the project status to "in progress."

This repository stores the XPaths and IDs needed to identify and interact with elements on the webpage. If these elements change, you only need to modify the data in the repository, and the changes will be reflected in all test cases that use this repository.

Benefits of repositories

• Centralization of resources: All information is stored in one place, making it easier to access and manage.
• Simplified maintenance: Updating a resource in the repository will automatically reflect in all linked test cases.
• Agile testing: The reuse of resources and centralization allow for faster and more efficient testing.

Maximize the efficiency of your tests with TAST

Using gates and repositories in TAST maximizes efficiency and improves the structure of automated tests.

Request your TAST demo with no commitment and discover more features that will make your testing team's work more efficient.