Has anyone else used Coverity or Klocwork in a Continuous Integration environment?
Posted by wenzi on 22 May 2006 at 11:15 am | Tagged as: (t) , (t) , (t)
If you have used coverity, klocwork in a agile development work, what were your opinions ? How many false positives did you find. Is it a waste of time of helpfull?
Just leave a comment below. I want to hear what you guys think.
I am thinking about using it in a continuous integration environment. Putting it in our build system, so it will run tests on a much more regular basis.
Here is a definition of CI copied from the AgileJournal
Continuous Integration. Maintaining an error free and functional code base is critical. Teams must synchronize changes with a source code repository and integrate modifications incrementally to ensure that the application is always functional. Adding changes to an already broken code base provides no value. When agile developers encounter a compile error or a failed unit test, they fix the problem immediately. This practice ensures that small issues are resolved before they become large. Initially, it may seem this approach impedes progress since development appears to move along at a slower pace. But delaying integration is delaying risk, and so continuously integrating code promotes a more sustainable rate of progress over time. An automated and repeatable build is the cornerstone of a robust continuous integration strategy.
And any thoughts on using tools such as PMD and emma would be greatly appreciated.
4 Responses to “Has anyone else used Coverity or Klocwork in a Continuous Integration environment?”
Leave a Reply
You must be logged in to post a comment.


I think the open source ones may be more popular with developers. I do not know the proce of Coverity , probably too much.
I dont think that many people use this stuff. I have been on a few programming gig where they really could have used it.
tests? what are tests?
we just let the user do the testing!
Any more posts on code coverage ?