Test manual & automation

To provide the right digital experiences, we need to test the products from start to finish, ensuring quality and usability throughout the entire process. Despite the fact that there is currently a trend towards test automation, in many cases manual testing is still the best option for certain tests and for certain developments. For this reason, at Qualis Lab we provide a comprehensive service in which, first of all, we define together with the client the Testing strategy that is required according to the needs.

What do we automate?

Test cases what:
- Are tedious or complex
- Recurring
- With a lot of interaction and validations
- They consume a lot of time

When do we automate?

We automate when:
- Critical time to market
- When we want to specialize the quality team
- Recurring deliverables
- Repetitive tests with a lot of interaction and validations

When do we not automate?

It is best NOT to automate when:
- When the system is not stable
- Specific tests
- Inconsistency of environments and data
- When the level of maturity is not reached


Manual tests are very important when it comes to testing functionalities, in a certain context. It implies that a person, based on test cases, handles himself as an end user would do in order to detect, report failures and finally ensure its correct operation. They are mainly used for functional, usability or exploratory tests.

The effectiveness of the combination of manual and automated testing has been proven, since testing automation is definitely not a replacement for manual, but rather a complement that ensures the best results in very efficient times. At Qualis Lab we ensure the best proposal to be able to take your products to a higher level in terms of quality and usability of digital applications.
There are different levels of testing and it is interesting to know to what extent we should automate them.


In a good test automation strategy, the generation of automatic scripts, the parameterization of tests, data management, the creation of a reporting system, the development of automation frameworks coexist, and all this is possible when behind the tools there is a team of experts who carry it out.

We work with the most recognized tools on the market:

What do we achieve this way?
 Greater homogeneity.
 Elimination of routine jobs.
 Reduction of the time spent in processing the information.
 Be competitive with the customer.
 Improve and optimize the implementation of analysis, functions and diagnostics.
 Improvement of product quality.

What are the most useful and effective tests and what are they for?

Functional Tests: to check the functionality of a system from end to end, from the user's perspective, and recognize adjustments or modifications.
Regression Tests: to verify that any modification that a system has undergone does not bring about modifications in other parts or functionalities of the system.
Smoke tests: to verify that your application has the minimum conditions to start your test cycle, as soon as development makes its deployment.
Health Tests: to verify that your productive application is in good condition without carrying out transactions, every day at fixed times or at the times you have.

What other tests do we do?

API testing: to test the backend directly using the services that are running in your applications.
Generation of Environments: to generate the necessary data and create your environments for both development and testing automatically.
ATM/ATS: We have experience generating automatic and semi-automatic scripts to test this type of terminal.
AS400 Mainframe Consoles: We automate both tests and core banking processes using AS400 consoles.
CORE Banking:We work on the Automation of tests of Core Banking systems. The requirements of financial regulators change regularly, so upgrading system components means not only improving performance and expanding functionality, but also ensuring the core functionality of the banking system. Consequently, regression testing costs increase with each new update.

They serve to validate the results of the operations carried out by our applications without the need to navigate through the UI, allowing us to save time in validating the operations carried out by our digital systems, exposing errors early and facilitating possible failures in the application layer business.
API: J meter, Neoload, Katalom, Postman, SoapUI

We test your apps on real devices and emulators to find bugs and deliver quality builds on time
In our testing lab, we continually innovate to ensure your apps are bug-free on all types of mobile devices, incorporating automated testing.

We realistically simulate millions of users, analyze the performance of your applications in high-demand situations, and monitor your servers under web stress.

At Qualis Lab we use specific tools that create and execute scenarios that emulate the reality of application use. This allows varying the number of transactions and concurrent users while monitoring the behavior of all infrastructure variables, measuring response times and the duration of business processes.

We are able to carry out load tests quickly, efficiently and frequently in order to quantify infrastructure capabilities and validate application performance, growth, stability, volume and scalability requirements. The objective of these tests is to ensure the performance of critical components and key operations for the business.

Test of performance:
These tests determine the responsiveness of the system under different performance scenarios that represent different peak times of use related to the operating calendar.

Volume tests:
These tests determine how and at what point your system's performance degrades when certain data throughput limits are exceeded. The main objective is to find weaknesses within the system for the processing of large amounts of data, that is, during the execution of batch processes.

Growth Tests:
The purpose of these tests is to determine the system's response capacity under different growth scenarios at 1, 3 and 5 years, which include load variations. The main objective is the generation of metrics that quantify the expected response of the system under expected conditions in the future.

Scalability Tests:
They allow us to determine if the system can scale according to the demand, depending on the different types of hardware configurations.

Stress tests:
The goal of these tests is to expose components of the system architecture to incremental load situations until they reach the point where performance degrades or availability is interrupted.

Availability tests:
These tests make it possible to identify if the 24x7 availability requirements of the selected services are vulnerable and under what conditions, as well as to understand the points of failure of the system and the need for redundancy.
We focus on working together with the best tools on the market.