Thorns and roses in migration testing

The product growth may result in the necessity for changing of core components working for a long time. And usual approaches are no longer usable. The requirement "it should work as it was before" can't easily turn to a test plan. We have to use new approaches, and the ironical phrase "code is requirements" suddenly turns into a working solution