Manual Testing
We carry out tests directly and manually, simulating the use of the end user in an application. We follow up on the tests performed with Jira or TestLink, ensuring that they meet the established criteria and requirements.
Compatibility Tests
We perform a variety of tests to ensure that each process performs its function correctly, covering the main platforms such as Web, Mobile and Desktop applications using tools such as BrowserStack or LamdaTest.
Automated Testing
Through the use of software tools such as Selenium, Appium, JUnit and TestNG, we execute repetitive tests automatically to reduce QA time with greater ease.
API testing
We perform API testing with Postman and Maven to verify that an application’s interface correctly meets its expected functionality and performance.
Security testing
Our quality engineers use Penetration Testing to identify vulnerabilities and flaws within an application to protect data, processes and access, as well as prevent threats.
Performance tests
We run different tests to determine the performance of an application using JMeter, as well as scalability, resource use, response times and speed.
Requirements
Our QA collaborators interact with the software team to analyze the code and project requirements.
Plannig
A test plan is made that helps identify the activities to be carried out and the time in which each test must be completed that will verify compliance with the needs established in an application.
Design
Our QA collaborators design the test cases and prepare the scripts necessary to validate each section of an application.
Execution
All functional, security or performance testing is performed, and test cases and scripts are executed manually or automated as needed.
Defects Management
At the end of the test execution, the identified errors are managed, documented, prioritized, the impact they generate on the system is analyzed, and a resolution to the defects is provided.
Closing
Managed defects are sent to the development team so that the necessary corrections can be implemented. Once the fixes are completed, each reported bug is again verified before closing it.
