Loading ...
Sorry, an error occurred while loading the content.

11278Re: [XP] Refactoring legacy code

Expand Messages
  • Peter Schrier & Narda Bergsma
    Sep 1 12:04 AM
    • 0 Attachment
      Most times, bugs are detected in the UI by the end-users. So, to prove that the
      user is right about the bug, you have to write a Functional Test which reveals
      it. Then you have to track it down to your code, make a UnitTest for it and fix
      the code, UnitTest to make sure the bug is squashed, and FunctionalTest to
      prove that for the user the bug is removed as well.

      Peter Schrier

      Quoting Mark Wilden <mark@...>:

      > ----- Original Message -----
      > From: "Michael C. Feathers" <mfeathers@...>
      > >
      > > For every bug you fix, make sure it is reflected
      > > in a functional test and in a unit test.
      > Of course, you write the test before you fix the bug. Also, I don't think
      > it's necessary to explicitly include detection of the bug in a functional
      > test, if a unit test already does it. It depends how massive and visible
      > the
      > bug is, I guess.
      > To Post a message, send it to: extremeprogramming@...
      > To Unsubscribe, send a blank message to:
      > extremeprogramming-unsubscribe@...
      > Ad-free courtesy of objectmentor.com
    • Show all 28 messages in this topic