Quality Assurance for Legacy Code

Our team plans to redefine part of the module in the obsolete code base. This is a web application written in java. It has no unit tests at all.

I asked the developer to write junit for existing functionality before re-factoring, but I'm sure it will not be very extensive.

what other measures (blackbox / whitebox / processes) can I take to make sure that re-factorization does not violate existing functions.

The current system is quite stable and has been working for over 8 years.

Thank you Gray

+3
source share
3 answers

Michael Feathers " " .

, ( , , ). , , , , ; - . , - - . , TDD , .

+2

: , . - . , , , .

, . , , () , ? , , . , qa-, , .

+1

Besides writing more units, you can always write test scripts using JMeter. Include statements to make sure you get the expected results.

0
source

Source: https://habr.com/ru/post/1776463/