Agree. I use it within Eclipse for developing Tuscany code once a while. It's useful for better code.
We don't enforce these tools at maven build level. Developers are welcome to use them locally though. Raymond Feng Sent from my iPhone On Jan 25, 2011, at 5:33 AM, dsh <daniel.hais...@googlemail.com> wrote: > I would say TDD and static code analysis are complementary. > > Cheers > Daniel > > On Tue, Jan 25, 2011 at 11:07 AM, Mike Edwards > <mike.edwards.inglen...@gmail.com> wrote: >> On 24/01/2011 18:13, César Couto wrote: >>> >>> Dear developers, >>> >>> I am a PhD student at UFMG, Brazil and as part of my research I am >>> making a study about the relevance of the warnings reported by the >>> FindBugs bug finding tool. >>> >>> Since I am planning to use Tuscany as a subject system in my research, >>> I would like to know if Tuscany's developers usually run FindBugs as >>> >>> part of the system development process. >>> >>> Thanks in advance, >>> >>> Cesar Couto >>> >>> -- >>> http://www.decom.cefetmg.br/cesar >> >> Cesar, >> >> I can't speak for all Tuscany developers, but I can say that I don't use >> FindBugs and I am not aware of anyone who does. >> >> Our approach in Tuscany is more Test Driven Development, where the >> development process is led by the creation of testcases which are used to >> drive and check the development or modification of code. >> >> The advantage of this general approach is that we build up a set of >> testcases that are then used to validate all future changes in the codebase >> - and which quickly expose any problems caused by code modifications and >> code additions. >> >> The main problem with test driven development is in getting a sufficiently >> extensive set of testcases - some situations can be difficult to model (eg >> code running in multiple separate JVMs), plus there is the inevitable >> failure of imagination and/or foresight as to how the code will be used. >> >> >> Yours, Mike. >>
