Re: DNA TCK?

Hi,

From: "Leo Simons" <[email protected]>
> > * all the different combinations of lifecycle interfaces
> > * verified lifecycle stages called in correct order
> > * verified that all resources passed in were non-null
> > * verified that all the resources passed in matched corresponding
metadata
> > (ie conformed to schema, had correct resources present, etc)
>
> and I'm sure more bullets will be found :D

yep.

> I'm sure it can be done. Maybe you could have several "bad" components,
> and some abstract test cases of some sort that tries to load them into
> the container. You then use some kind of "invocation recorder" inside
> each component that records the component state.

sounds possible.

> never really built something like this before, so I don't know yet. But
> I think it can be done (Sun has a J2EE TCK, don't they? And that's some
> complex rules as well :D).

yep but they also have non-automateable steps IIUC

> I'm relatively sure a TCK can be developed
> using baby steps, just like everything else...

yep.

> Atm I'm just figuring out if there's enough interest (and perhaps people
> who feel like helping out). It's a bit silly to build a big kit, then
> have no-one who wants to test their container passes the test :D. I'm
> likely to tackle the simpler stuff first (maybe I'll try and refactor
> the pico TCK to run without requiring the PicoContainer interface, for
> example).

Well it is definetly something worth doing and FWIU it could easily be
generalized to be a something that you could also use to unit test the
Avalon stuff aswell if you are still involved with that. Anyways would be
interesting to do and will gladly commit and help develope any stuff you
contribute ;) I will also probably add an Avalon layer on top as we still
need that for Loom.