Technical debt is often overlooked, and it is essential to take it into account. Testers are committed to adapting test cases, test plans and frameworks in line with changes throughout the development process, in order to minimize the number of components that are no longer useful and optimize resources.“Jorge Asensio, test automation expert at q-leap.
Technical debt encompasses everything that is directly or indirectly linked to the software under development, and which is no longer useful to the development process or to the maintenance of the application under development.
Process debt is a kind of technical debt generated when processes are poor or absent for handling things like defects, documentation or even test cases.
Some form of technical debt will always exist. There are organizations that fight valiantly to contain it, and others that have left “I.O.U.’s” plastered in various places as reminders to “clean up failed unit tests”, “redo documentation”, “update application dependencies” or “refactor old code”. These tasks continue to be pushed back into the backlog while more important business stories are dealt with.
As a tester, watching developers struggle to repay even minor technical debt is a struggle with which we should sympathize. Testers, along with their software development partners, tend to advocate cleaning up technical debt for the sake of quality. One area that testers generally have to deal with is process debt. This eats into time that would be better spent testing the software, just as technical debt eats into development time.
Read the full article on the Ministry of Testing.
ABOUT THE Q-LEAP EXPERT RECOMMENDING THIS ARTICLE
Jorge Asensio is a test automation expert at q-leap. Jorge is a tester who likes to share his experiences and learn from others.
He is a strong team player, has excellent customer communication skills and is fully dedicated to his career in software testing. His focus is always on perfection in terms of automation, functionality and performance. He is also an expert in Selenium Browser Automation, a framework for automating online applications. Jorge works closely within the company to help evaluate and improve existing automation frameworks, design, run and maintain automated test scripts to ensure quality control standards are achieved.
