Re: Number of tests per line of java code


"Noah Fiedel" <nfiedel@xxxxxxxxx> wrote in message
news:1118097632.821747.209270@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> Lucy,
> From years of experience, it sounds like this project is set up to
> be a failure. If you don't have specs, you will not ever be able to
> write full, complete, accurate tests. 225,000 lines of code doesn't
> mean much. I took over a project with 13,000 lines of code - much of
> which was refactored out as it was a hard-coded static database! In
> another project, I spent many months painstakingly working with a 6,000
> line set of existing code. Only now that I understand this undocumented
> code can I tell you - I could have fully re-implemented it, with
> documentation, with better features & reliability, in far less time.
> If your management is stuck on the idea of reusing this code -
> which sounds like it was from either (a) an outsourcing firm that
> disappeared, (b) an aquisition or group that was laid off, etc... you
> should have them take a look at the comments here and re-evaluate the
> project.
> To succeed well in any project, you will need a clear direction and
> goal. Simply adding tests to existing code will not serve that purpose.
> Any existing bugs for example will probably be overlooked by the code,
> if you do not know that they are bugs when writing the tests.
> Best of luck,
> Noah
>

They are not stuck on the idea, they want information that will allow
them to choose whether to 1) start from scratch, 2) use and modify
the existing code, 3) try to find another company to partner with, 4)
do nothing. A cost/time estimate will help in making the decision.
Thanks for your perspective.



.

Relevant Pages