Home / Press / Software & Architecture

Open Source

From a week to an hour: the transformation of QA in a project

How we transitioned from manual to automated testing, multiplying efficiency and reducing costs

N
From a week to an hour: the transformation of QA in a project

Before discussing results and improvements, to understand the impact of the changes in this project, it’s worth taking a moment to remember what the job of a QA (Quality Assurance) or tester entails. It goes far beyond identifying errors. Their role is to ensure that software meets quality, security, and functionality standards. Every application, system, or platform we use daily has undergone rigorous testing, designed to protect the user experience and prevent potential failures with economic, operational, or even security consequences. In a digital environment where reliability is key, testers are consolidated as guardians of technological efficiency.

In an interview with José Vicente Fayos, QA Analyst at MindDen, he explains the importance of this role very well:

 

 

“The response from the business was that it was a waste of time”

In this project, the MindDen team faced a common challenge in many companies: manual regressions consumed a full week of work for at least two QAs, slowing down deployments and increasing the risk of errors in production.

Launching the MVP (Minimum Viable Product), meaning the first version released to production, in that situation leads to a slow and costly process. One of our colleagues actively involved in this project explains it this way:

When a product doesn’t start with automated tests, the QA workload increases exponentially. This translates into saturated teams, less capacity for innovation, and higher operational costs.

And this is not an isolated case; in fact, it happens frequently. To begin changing this dynamic, a process was necessary. A proposal had to be presented that aligned with the needs of this project.

From weeks to hours: how we achieved it

Our team proposed a strategic and gradual solution: incorporate a junior QA for three months to support manual testing and free up time for the rest of the team, so they could automate tests in blocks and demonstrate progressive improvements to the business.

Our colleague summarizes it this way:

The results: higher quality in less time

The transformation was evident:

  • Today, regressions include more than 50 automated tests.
  • Time was reduced to 4 hours in series and barely 1 hour in parallel.
  • Performance, stress, and service tests were added.
  • Improved monitoring of unit tests and clarity of reports.

All of this with a direct impact on what matters most to our partners:

  1. Reduced operational costs.
  2. Speed and reliability in deployments.
  3. Motivated teams, focused on delivering real value.

A cultural, not just technical, change

The most valuable aspect was not just the technical advancement, but the change in mindset.
What was once considered a “waste of time” became a strategic pillar of the project.

At MindDen, we believe that investing in QA automation is not a luxury: it ensures quality, efficiency, and trust for the present and future of the product.

N
Nerea López — Redactora y Comunicación Mindden articles are written from real production projects and reviewed by the technical leads of each area.