We first have to agree on what 100% means.
I provided a very simple example in the earlier post.
The example gives a 100% tested tested method example,
given that the assumptions hold.
This example can be entirely generated using DataType
meta data.
Thus it's an immidiate result of using a modeling
approach to generating a solution / code.
It could be implemented by reading the defined
Operation into a model defining the additional meta
data for the Java DataTypes and then running a test
generator.
EMF already has a Java Parser for generating Ecore
Models from Annotated java code.
So this could be used.
My challenge to you now is describing unambiguously
how the point of diminishing return is reached through
a series of simple examples.
--- Cédric Beust â <
cbeust@...> wrote:
> On 1/2/07, Ole Ersoy <
ole_ersoy@...> wrote:
> >
> >
> > > * Getting to 100% tested takes less time if we
> > > generate tests from a
> > > model than if we write them by hand.
> >
> >
> > Sure - getting methods that are 100% tested should
> > take 0 time (For the person doing the coding).
>
>
> That's a very deceptive statement.
>
> Not only is it very hard to reach 100% testing (just
> because your code
> coverage claims 100% doesn't mean you are covering
> 100% of your code), but
> it's actually harmful to try to reach this goal.
> There is a point of
> diminishing return where you are better off
> improving your application that
> shooting for this elusive 100% testing.
>
> --
> Cédric
>
http://testng.org>
>
> [Non-text portions of this message have been
> removed]
>
>
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
