First of all welcome on board.
Well I have been thinking to make a post resuming all the discussion of
these days, but frankly I think it's better you read comments on blog
and on TSS. I got also some comments by mail, and I'll post about; I'm
waiting to understand if who sent me that comment would join this group.
I have also got some comment, suggestions and concerns by IRC contact,
but since Randal and John has joined this group it's probably better
they write they thought directly than I resume them. BTW John, Randall,
if you would prefer I post our chat transcript just ask I have saved the
log.
Well let me introduce each other: Randall and John are the 2 main
developer of JBoss DNA where I have met them during some small
contribution (I have very few spare time, but I hope to contribute some
more there guys). Alessio is a JBossian too, leading JBossWS. I have
been his former boss and he is one of my best friends. Luca is a
colleague of mine who have patiently stand me and my obsessive talks
about TestedBy during our lunch time.
Probably is better to focus on what are the 2 keys point of TestedBy:
1. Run test on interfaces. IOW API designer define not only
signatures but also behavior their interfaces are supposed to
provide. They provide not only interface definitions, but also
unit tests verifying supposed behaviors. TestedBy does the magic
of run test on all implementations ensuring not only signatures
are right, but also supposed behavior are provided (of course
implementations may add behaviors). It apply also to a DbC approach
2. Run automatically tests on modified interfaces. It could be a a
great added value if done directly by IDE during development.
Ok, let's start discussing all what you don't like in these approach
and/or about blog post.
BTW I can see we have a lot of work mainly in 4 areas: Eclipse, ant take
(and maven in next future), core to execute tests, core to round trip
tool. Volunteers ;)?
Thanks to all for the interests
S.