This week's book giveaways are in the AI and JavaScript forums.
We're giving away four copies each of GANs in Action and WebAssembly in Action and have the authors on-line!
See this thread and this one for details.
Win a copy of GANs in ActionE this week in the AI forum
or WebAssembly in Action in the JavaScript forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
  • Campbell Ritchie
  • Bear Bibeault
  • Paul Clapham
  • Jeanne Boyarsky
  • Knute Snortum
  • Liutauras Vilda
  • Tim Cooke
  • Junilu Lacar
Saloon Keepers:
  • Ron McLeod
  • Stephan van Hulst
  • Tim Moores
  • Tim Holloway
  • Carey Brown
  • Joe Ess
  • salvin francis
  • fred rosenberger


Posts: 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Ranch Hand
Posts: 508
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I agree testing is an important part of Refactoring.
This testing related web site does recommend the Refactoring book though.
"Refactoring--improving the design of existing code" by Martin Fowler. I think it is the first click on the left at the top of this forum.
Posts: 6920
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Testing is so important that some Extreme Programming authors consider it a prerequisite for refactoring. If you can't test that your software performs the same after your refactoring as before, then refactoring can become too risky and too expensive to take on.
In theory, each refactoring is designed to have no effect on the overall function of the software, but in practice the process of refactoring can cause behavioural changes. For systems (like Java) which currently have little or no automated support for refactoring, there is always the chance that the programmer might type something wrong, edit the wrong file, delete some code by mistake, whatever. There is also the possibility that a refactoring might excercise a bit of code which has never been fully tested, or is poorly named or misunderstood.
So to enable carefree use of refactoring, a good and fairly comprehensive regression test harness (or at absolute minimum a good set of test cases) is extremely useful. The one-two punch of automatic regression testing and rigorous refactoring (rather than just tikering) is capable of delivering real development and maintenance benefits, and potentially more than the sum of its parts.
Why should I lose weight? They make bigger overalls. And they sure don't make overalls for tiny ads:
Java file APIs (DOC, XLS, PDF, and many more)
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!