To be honest,testing the quality involves the logic of the programs
-how well has that been achieve d? will that ensure better code
deliverables for functionalities written on it.

I would like to see metrics being implemented on the samel.

Regards,
jd

On 6/18/10, Mahmood Ali <notn...@gmail.com> wrote:
>> He actually said that tests were a luxury?
> I think his point is that "100% unit test coverage" is a luxury.
> There is more to testing than unit testing.  Joel has been critical of
> TDD and unit tests in general, but has been an advocate of testing in
> general [1], especially manual/integration/exploratory testing.  While
> the culture of unit testing has probably advanced code quality over
> all, it's a bit unfortunate that code quality metrics have been
> reduced to unit testing for many programmers.
>
>> If your code doesn't work, who cares how quickly you can get it done and
>> put
>> out into the wild.
> The value of testing and software quality control is a bit interesting
> and quite a bit hard to measure.  On one hand, if the software is
> completely broken and cannot be used, it's clear that you should hold
> on shipping; on the other hand, if the software has a bug with very
> limited impact (e.g. blogging software that doesn't account for leap
> seconds properly) shouldn't hold off the release of the code.  This
> dilemma and forces are recognized in the Project Triangle[2].
>
> A good project manager (and hopefully a good engineer as well) should
> measure the value of testing/quality with respect to delivering on
> time.
>
> The problem with assessing code quality is that the actual cost is
> mainly a future cost, which cannot be estimated well.  So one ends up
> undervaluing it (and then we end up in another Y2K situation).
>
>  - Mahmood
>
> [1] http://www.joelonsoftware.com/articles/fog0000000067.html
> [2] http://en.wikipedia.org/wiki/Project_triangle
>
> --
> You received this message because you are subscribed to the Google Groups
> "The Java Posse" group.
> To post to this group, send email to javapo...@googlegroups.com.
> To unsubscribe from this group, send email to
> javaposse+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/javaposse?hl=en.
>
>

-- 
You received this message because you are subscribed to the Google Groups "The 
Java Posse" group.
To post to this group, send email to javapo...@googlegroups.com.
To unsubscribe from this group, send email to 
javaposse+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/javaposse?hl=en.

Reply via email to