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

Re: [XP] Do you change your tests?

Expand Messages
  • J. B. Rainsberger
    ... Bingo! Open/Closed is a destination, not a goal. Keeping the design simple helps code that wants to close become Closed. ... J. B. (Joe) Rainsberger ::
    Message 1 of 8 , Dec 25, 2007
    • 0 Attachment
      On Dec 21, 2007, at 01:02 , John Maxwell wrote:

      >
      > On Thu, 2007-12-20 at 21:20 +0100, Carlo Bottiglieri wrote:
      > > On Dec 20, 2007 4:15 PM, brianhvictor <homeusenet3@...>
      > wrote:
      > > >
      > > > --- In extremeprogramming@yahoogroups.com, John Maxwell
      > <jmax@...> wrote:
      > > > > Your two questions are orthogonal; when the desired behavior
      > changes,
      > > > > the test _must_ change to reflect the new behavior. How to go
      > about
      > > > > making the newly changed test pass depends on the details of
      > the code.
      > > >
      > > > This is where I'm confused, though. I recently discovered the
      > > > open/closed principle and I'm trying to wrap my head around it. It
      > > > seems to be implying that behavior should never change.
      >
      > I see it more of an observation about good code than a guide for
      > structuring changes.
      >
      Bingo! Open/Closed is a destination, not a goal. Keeping the design
      simple helps code that wants to close become Closed.
      ----
      J. B. (Joe) Rainsberger :: http://www.jbrains.ca
      Your guide to software craftsmanship
      JUnit Recipes: Practical Methods for Programmer Testing
      2005 Gordon Pask Award for contribution Agile Software Practice
    Your message has been successfully submitted and would be delivered to recipients shortly.