We built a formula to estimate the effort to write characterization tests on our Legacy C application, with the goal of transferring the knowledge to another team, or during an outsourcing.

What about our results? What kind of objections could we face? What would be an acceptable action plan?

• En français : Application Legacy – Refactoring ou reengineering? (VII)
• In English: Legacy application – Refactoring or reengineering? (VII)
• En Castellano: Aplicación Legacy – ¿Refactorización o reingeniería? (VII)

We want to write characterization tests on our Legacy C application, with the goal of transferring the knowledge to another team, or during an outsourcing.

What should be the scope of this ‘characterization’? When can we consider that our test coverage is sufficient? Is it possible to quantify the effort it represents?

• En français : Application Legacy – Refactoring ou reengineering? (VI)
• In English: Legacy application – Refactoring or reengineering? (VI)
• En Castellano: Aplicación Legacy – ¿Refactorización o reingeniería? (VI)

Following of our previous post about characterization tests, for our Legacy C application.

• En français : Application Legacy – Refactoring ou reengineering? (V)
• In English: Legacy application – Refactoring or reengineering? (V)
• En Castellano: Aplicación Legacy – ¿Refactorización o reingeniería? (V)

Back from summer vacations and back on this series about Legacy code. In this post, we will talk about the importance of unit testing in order to understand and a Legacy application, before to start any change.

• En français : Application Legacy – Refactoring ou reengineering? (IV)
• In English: Legacy application – Refactoring or reengineering? (IV)
• En Castellano: Aplicación Legacy – ¿Refactorización o reingeniería? (IV)

Enjoy!