Hi,
In the latest calculator sample, it demonstrates the usage of itest where we
define a harness composite as follows:
<composite xmlns="http://www.osoa.org/xmlns/sca/1.0";
xmlns:tuscany="http://tuscany.apache.org/xmlns/sca/1.0";
name="CalculatorTestHarnessComposite">
<include name="CalculatorComposite"
scdlResource="META-INF/sca/default.scdl"/>
<component name="testComponent">
<tuscany:junit class="calculator.CalculatorTestComponent"/>
<reference
name="calculatorService">CalculatorServiceComponent</reference>
</component>
</composite>
I think we might be able to further simplify this by introspecting the test
cases to create such a harness composite. For example, we can create a Junit
component if the base class is org.junit.TestCase and use autowire to
resolve the references to the services being tested. Does it make sense?
Thanks,
Raymond
----- Original Message -----
From: "Jeremy Boynes" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Monday, February 12, 2007 10:40 AM
Subject: Re: Runtime bring-up and next steps
On Feb 12, 2007, at 9:46 AM, Jim Marino wrote:
On Feb 12, 2007, at 8:01 AM, haleh mahbod wrote:
Does bring up of runtime include a successful run of iTest?
I was specifically referring to the standalone runtime but it appears
Jeremy also has the itest plugin working with the really neat ability to
run a JUnit test as a component. This looks like a big improvement over
the old SCATestCase, particularly since it is closer to the 1.0 APIs (we
discussed doing this a while back). I'll let Jeremy comment more on
it...
I went to work on the proposal for updating the itest framework and have
the basic framework going. There is a smoketest in the runtime model that
basically brings up a test component and calls it.
I've started porting the samples from M2 to the 1.0 spec, starting with
ones that do not use any extensions. I created a new core- samples module
for this. I've managed to itest the calculator with the plugin.
The launcher and webapp runtime these use don't work yet as they need the
contribution stuff Luciano is working on - I had to hack local deployment
into the itest plugin to be able to run things. Until then, I'm going to
start migrating the old itest to 1.0 using the plugin to test them. If it
seems to work well, I'll add doco to the plugin to generate the typical
mini-site.
We could also use a hack similar to the one I used in itest to deploy
composites locally for the standalone and webapp environments - I can
give pointers if anyone is interested (see
MavenEmbeddedRuntime#deployTestScdl).
--
Jeremy
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
