From the author of "Working effectively with legacy code", Michael Feathers, a blog post on "Refactoring needs more than tests". Interesting point of view: sometimes unit tests are not enough when it comes to refactoring.
M.F. disusses the situation of a project with a large code base, where several teams work on different releases/branches of the code at the same time. How do you refactor with confidence in this case? Another scenario discussed in the post is a project with dependencies on 3rd party code. How do you refactor with confidence, when you know that the 3rd party code keeps changing and needs to be patched everytime it gets updated?
Michael's answer is: integrate frequently. I say: buildbot to the rescue! :-)
Subscribe to:
Post Comments (Atom)
-
This post is a continuation of my previous one on " Running Gatling tests in Docker containers via Jenkins ". As I continued to se...
-
For the last month or so I've been experimenting with Rancher as the orchestration layer for Docker-based deployments. I've been pr... -
Here's a good interview question for a tester: how do you define performance/load/stress testing? Many times people use these terms inte...
No comments:
Post a Comment