By bloid
via anthillpro.com
Published: Jul 16 2008 / 13:54
It's about tests not builds
While rereading Martin Fowler's classic paper, Continuous Integration, it struck me that its approach to Continuous Integration (CI) is fundamentally flawed. Fowler, like most of the CI community, seems to argue that CI is about building rather than testing. This basic misconception, permeating an otherwise good paper, has contributed to poor tool designs that are focused on build automation and, perhaps more importantly, an untold numbers of teams following bad practices
-
top 10 most usefull Add-Ons for Your Browsers
-
Two Leading Cloud Service Providers Select MSPexcellence to Enhance Their Indirect Channel Programs
-
A business component architecture with Spring 3.0/3.1 – Part 3: Properties
-
Recent Apps We've Open Sourced
-
Results of Joel Spolsky's "What Programmers Want" Survey
-
Cloudshift - A Node.js App Framework for haXe Programmers
Comments
MichaelMinella replied ago:
Interesting perspective. However, I have to disagree. Although tests are a pivotal piece of CI, it is not the key piece. Constant feedback, IMHO, is the key piece. That feedback comes from a barrage of sources. The results of testing is one source. However, a good CI system will also do a deployment to a test environment and expose it to QA which provides another source of feedback. Yet another source would be your business owners taking a look at the functionality during development and providing feedback and course correction. It is this feedback that is the key point in CI and any Agile process.
Voters For This Link (9)
Voters Against This Link (4)