We propose a work scheme that allows us to adapt to projects with traditional or agile methodologies. Our main objective is to generate value and ensure the non-functional quality of the solutions.
We have a performance strategy, which adapts to the particularities of the application architecture, where we intend to automate the tests in the appropriate layer to obtain the best cost-benefit ratio.
We work focused on the triangle of synergy to articulate an entire performance culture.
We promote synergy in teams based on 3 dimensions:
By working in these dimensions, we seek to implement changes in the culture so that they last over time.
Did you know that making load tests in an advance stage of the development lifecycle involves taking serious risks?
At Sofka, we provide a performance testing service with a clear methodology that allows establishing activities related to non-functional quality from the early and continuous stages of the development life cycle.
- Mitigating risks of application failure
- Reducing overall expenses
- Meeting response times.
We are clear that by building a base of early performance tests, we achieve greater benefits in terms of:
- Execution Speed
Performance DevOps (CPT)
Automatic and repeatable performance tests generate constant feedback of the impact that each change has on development, either within the project deployment line (pipeline) or separately as a repetitive task that alerts over performance degradation.
Performance IAC (Infrastructure as code)
It allows to preserve the infrastructure in recipes that can be replicated and adapted to the need, achieving:
- Having controlled, tested and integrated versions
- Lower cost
It is important to have reliable, cross-sectional and real-time monitoring of all projects, a large part of the success depends on the adequate visibility of the infrastructure status and the adequate implementation of alarms that allow to react quickly and preventively to the degradation of quality levels, such as response times and availability percentages.
The objective is to always avoid the unavailability of the service, reducing economic losses and preserving the company’s prestige.
- Maximize availability.
- Save time, energy and money.
- Act quickly
Types of performance tests
Sets the response speed of a system under a certain load. Considering the expected maximum number of users for critical transactions, this enables you to determine if the system is ready for service level agreement (SLA) compliance and to deliver business value.
Indicates whether an application will retain its serviceability for a long period of time. Determine if, for example, the application's resource consumption will remain stable or if there are other glitches that could compromise the stability of the application. A common example of a stability problem would be a slow growing memory leak.
Recovery tests are performed to verify how quickly and how well an application recovers after experiencing a hardware or software failure. Therefore, performing recovery tests requires forcing a failure and then verifying if recovery occurs properly.
Recommendations for optimization of load times based on the evaluation and prioritization of calls, reduction of bandwidth expenses, reviews of code performance and optimization of Database queries.
Helps to determine that the current system meets the intended load. The results of the scalability test can be used to plan a future growth.
It validates whether a system can handle large volumes of data, calculations and processing.
Determines the maximum volume that a system can handle. A high enough load is generated to push the application to its maximum level and evaluate how it responds to these situations.