Testedby

[Jochen Mader]

I have been thinking about the issue that testby addresses for quite
some time.
We have the several scenarios where people have to start copy'n'paste to
do the tests and that is always a source of a lot of frustration.
For me JUnit is a great tool but ignores one of the most important
principles of OO-development "code to an interface".
I'd also be happy to contribute and help with this project.
Cheers
Jochen
--
Jochen Mader
Development Lead
Dipl. Inf. (FH)
+49 941 604889701

Pramari
Bruderwöhrdstr. 15b
93055 Regensburg

[Stefano Maestri]

Hi,
first of all welcome on board to you too.

Jochen Mader wrote on 13/11/08 22:46:

> For me JUnit is a great tool but ignores one of the most important
> principles of OO-development "code to an interface".
>

Yep, IMHO it's one of the most important feature we would provide with
testedby.
And as Junit ignores interface, Java ignores DbC. And contracts really
complete the interface definitions. Java interfaces are pure type
definition, without semantic, but semantic is the essence of development.

> I'd also be happy to contribute and help with this project.
>

Great, your background? In which part are you mainly interested? We have
a lot of open fronts.

> Cheers
> Jochen
>

bye
S.

[Jochen Mader]

> Great, your background? In which part are you mainly interested? We have
> a lot of open fronts.

I guessed so ;)
Rigth now I am development in the Rifidi project.
My main area of interest right now is SOA (using Equinox and Spring) and
for that area JUnit, in my eyes, is quite useless.
Just an example usecase:
We are using services to register different kinds of RFID-Readers to our
emulation. There is a baseset of interfaces that each reader needs to
implement to be available in our register.
Using JUnit to test the readers requires either copy'n'past or doing
weird tgings with JUnit.
Testedby would be a perfect fit for this scenario.
I'm from a strong JEE, OSGi, Eclipse and OpenGL background.
Rigth now I am mostly working with Eclipse RCP and OSGi.

CU

[Stefano Maestri]

Risposte in linea
Answer inline

Jochen Mader wrote on 16/11/08 13:20:

>
>> Great, your background? In which part are you mainly interested? We have
>> a lot of open fronts.
>>
> I guessed so ;)
> Rigth now I am development in the Rifidi project.
> My main area of interest right now is SOA (using Equinox and Spring) and
>

it's mine too, using JBossESB.

> I'm from a strong JEE, OSGi, Eclipse and OpenGL background.
> Rigth now I am mostly working with Eclipse RCP and OSGi.
>
>

Ok, so would you consider to lend an hand in Eclipse plugin? Or would
you prefer something else?

Anyway I'll try to define a precise roadmap very soon (I'd like tonight,
but I can't promise...for the end of the week for sure)

BTW, your timezone? I'm on GMT+1 (Italy)

cheers
S.

[Jochen Mader]

> Ok, so would you consider to lend an hand in Eclipse plugin? Or would
> you prefer something else?

Whereever help is needed. Eclipse is quite a big part of my daily work
so I'd be happy to help you out there.

>
> Anyway I'll try to define a precise roadmap very soon (I'd like tonight,
> but I can't promise...for the end of the week for sure)

Great.

>
> BTW, your timezone? I'm on GMT+1 (Italy)

Same here (Germany)

[Shih-gian Lee]

> I guessed so ;)
> Rigth now I am development in the Rifidi project.
> My main area of interest right now is SOA (using Equinox and Spring) and
> for that area JUnit, in my eyes, is quite useless.
> Just an example usecase:
> We are using services to register different kinds of RFID-Readers to our
> emulation. There is a baseset of interfaces that each reader needs to
> implement to be available in our register.
> Using JUnit to test the readers requires either copy'n'past or doing
> weird tgings with JUnit.

This sounds like you are doing more of an integration testing than
"unit" testing, or I may be wrong. Can you elaborate? I try to
understand your need.

Thanks,
Lee

[Jochen Mader]

> This sounds like you are doing more of an integration testing than
> "unit" testing, or I may be wrong. Can you elaborate? I try to
> understand your need.

Yes, integration testing is one of our problems.
In our current process we have people from universities implement
emulations of readers and their emulations need to integrate with our
stuff which results in unittests being copied around or nasty hacks.
Being able to ship the set of interfaces to be implemented with a set of
testedby classes would make things a lot cleaner.

My second area of problems is OSGi.
We defined the behaviour of a service with an interface, a set of umls
and did the unit tests.
For some services we only created a mock and decided to come back later
on to make it better. So you come back, start a new project, copy and
paste your unittests over and start to implement the service.
The copy and paste part gives me a lot of headaches and getting rid of
it would make the process a lot cleaner.
>From time to time you will also have several services that implement the
same set of interfaces. Copy and paste again and after refactoring a
little suddenly things start to get weird.
I know that these are worst case scenarios, but given the time that the
problems will have to evolve from this scenario combined with some lazy
developer results in a degenerating codebase.
CU
Jochen