Skip to main content
replaced http://programmers.stackexchange.com/ with https://softwareengineering.stackexchange.com/
Source Link

For legacy GUI applications you would benefit two ways:

  1. Business logic track: ask sb with business knowledge for descriptive info and write UI end-to-end automated tests. You get a good test suite for regression.

  2. Code contemplation track: if I were to write unit tests for legacy code I would do it only either for refactored or debugged code. IMHO there is no much use unit testing legacy code just to obtain regression tests set. This is whyThis is why

For legacy GUI applications you would benefit two ways:

  1. Business logic track: ask sb with business knowledge for descriptive info and write UI end-to-end automated tests. You get a good test suite for regression.

  2. Code contemplation track: if I were to write unit tests for legacy code I would do it only either for refactored or debugged code. IMHO there is no much use unit testing legacy code just to obtain regression tests set. This is why

For legacy GUI applications you would benefit two ways:

  1. Business logic track: ask sb with business knowledge for descriptive info and write UI end-to-end automated tests. You get a good test suite for regression.

  2. Code contemplation track: if I were to write unit tests for legacy code I would do it only either for refactored or debugged code. IMHO there is no much use unit testing legacy code just to obtain regression tests set. This is why

Source Link

For legacy GUI applications you would benefit two ways:

  1. Business logic track: ask sb with business knowledge for descriptive info and write UI end-to-end automated tests. You get a good test suite for regression.

  2. Code contemplation track: if I were to write unit tests for legacy code I would do it only either for refactored or debugged code. IMHO there is no much use unit testing legacy code just to obtain regression tests set. This is why