robert burrell donkin wrote: > one interesting consequence of a general move within jakarta towards > extensive unit testing is that the time required to commit patches has > significantly increased. my experience now is that creating good unit > tests takes more than the time it takes to write the code. i'm also now > more aware that good documentation is crucial and spend more time > creating documentation. this increases the time required to review and > approve patches from developers. as code bases become more mature, more > and more care also has to be taken when committing patches. it's rare > that i can review and commit any patch in less than an hour. i only have > a certain amount of time available for work on apache projects and so > the rate of improvement either slows or more bodies are required. i'd be > interested to discover how other, longer established projects solve > similar problems.
Presumably the idea behind unit testing is that it reduces the time spent chasing bugs. If the overall effect is not less developer time used per "unit of functionality", then I have to wonder what the point is. Cheers, Ben. -- http://www.apache-ssl.org/ben.html http://www.thebunker.net/ "There is no limit to what a man can do or how far he can go if he doesn't mind who gets the credit." - Robert Woodruff --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
