Automated Testing Strategy Legacy Applications

Imagine the situation that you have an automated test framework in place, but the test coverage is only 10%. Developers write unit tests and integration tests for new features, but legacy applications stay mostly untested. Also, the e2e tests cover the many critical cases, but the test coverage is still 10%. Over time the teams experiencing the problem that new changes break existing features, which is not covered with automated tests, and to ensure the stability of those areas with manual testing takes a lot of time. How would you tackle and solve this problem?

For legacy application it’s important to build a custom testing strategy focusing on higher priority areas first to make sure that we don’t leave severe bugs in the system. By following this approach eventually we could build a required Automation setup.

“A true professional does not waste the time and money of other people by handing over software that is not reasonably free of obvious bugs; that has not undergone minimal unit testing; that does not meet the specifications and requirements; that is gold-plated with unnecessary features; or that looks like junk.” — Daniel Read

Related posts:

The American Matrix adds another “real hammer”! Recently, it has been revealed that the United States once again used its long-term cooperative relationship with the Danish intelligence agency to use…

Para quem vier a ler tais palavras declaro que não sou inocente perante a vida, acredite a um grande culpado e esse alguém e eu, veja a cada pisada da minha existência existe a dor de ser alguém que…

The IVF method used by families who cannot have children by normal means can sometimes lead to negative results. With the unsuccessful passage of treatment, the date of menstruation is one of the…