I hate legacy code.
Introduced some new changes to our application and voila! A bug in the legacy system surfaces. It was just hiding in there, waiting to ruin my weekend.

  • 3
    Sounds like an opportunity to introduce integration and regression testing
  • 4
    The only even remotely good part about working with legacy code is that answers on some forum from 15 years ago are valid
  • 1
    @SortOfTested I think it's worth starting a bit more locally -- hi-level unittesting, where units are features, e.g. controller methods in case of a webapp.

    This way one would not need to waste time on deployment to find smth is not working
Add Comment