Re: Code Coverage and QC
From: Robert C. Martin (unclebob_at_objectmentor.com)
Date: 03/31/04
- Next message: Phlip: "TDD in a nut shell"
- Previous message: Ronald E Jeffries: "Re: xp and simple design"
- In reply to: thoff: "Re: Code Coverage and QC"
- Next in thread: Daniel Parker: "Re: Code Coverage and QC"
- Reply: Daniel Parker: "Re: Code Coverage and QC"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Tue, 30 Mar 2004 23:41:03 -0600
On Tue, 30 Mar 2004 16:33:09 -0800, thoff <tmh@possibility.com> wrote:
>
>
>Jason Nocks wrote:
>> No, this is incorrect. Writing new code to replace old code is
>> rewriting, not refactoring! They are fundamentally different. This is a
>> common misconception.
>
>Jason, you are clearly on some kind of crusade on this.
>I understand what you are saying, but i do not agree
>on the strictness of your use. I don't think very
>many other people use refactoring to mean what you
>mean either.
While the term "refactoring" has fallen into common usage meaning
"change the code" the original intent, and the definition still used
in XP is:
1. Refactoring. Noun. A very tiny modification to a program that
changes it's structure but does not change it's behavior as described
by existing unit tests.
2. Refactor. Verb. The act of making one or more refactorings to a
program for the purpose of improving it's structure.
-----
Robert C. Martin (Uncle Bob)
Object Mentor Inc.
unclebob @ objectmentor . com
800-338-6716
"Distinguishing between the author
and the writing is the essence of civilized debate."
-- Daniel Parker
- Next message: Phlip: "TDD in a nut shell"
- Previous message: Ronald E Jeffries: "Re: xp and simple design"
- In reply to: thoff: "Re: Code Coverage and QC"
- Next in thread: Daniel Parker: "Re: Code Coverage and QC"
- Reply: Daniel Parker: "Re: Code Coverage and QC"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|