On Feb 10, 2007, at 9:06 AM, Luciano Resende wrote:

Hi Jeremy

I'm working on a implementation based on a slightly updated model that Raymond had proposed and already committed to trunk. I should have something
in the next couple days available.

OK, thanks.

For the itest plugin, I would like to have a processor that can scan the test classes and find all test harness classes. I think can do this by providing an implementation of a SureFireTestSuite that can look for tests in one of two ways: 1) it can load a SCDL file from the test tree, find the components with <tuscany:junit> implementations and add them to the suite, or 2) scan the test tree identifying test classes, introspect their references, create components for them with <tuscany:junit> implementations, and autowire them to components in the composite- under-test

The first one is simpler to implement but requires that the user writes/maintains a SCDL file which is a bit of a hassle. I'm going to start with this as I can see that in some circumstances they will need to customize the assembly (so we'll need it anyway).

Both of these are a form of contribution introspection (the contribution being the test tree) - is there an interface I should be implementing to integrate with your stuff?

--
Jeremy


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to