On Oct 18, 2006, at 8:53 AM, Raymond Feng wrote:
+1 from me.
I can help as well. I already have a simple mortage approval
application in my sandbox and I'll convert it to whatever
integration test environment we come out when it's ready.
What I'm messing with is a maven plugin that can be attached to the
integration-test phase of the build. I added Mojo that starts/stops
the server and managed to bind the surefire plugin to the integration-
test phase to get it to run integration tests - this would allow us
to write the test clients using JUnit or TestNG. However, I'm
wrestling with the issue about how to make sure the test application
and the client run in compatible classloaders - I am afraid at the
moment that they will end up using different ones which would make
life awkward. I've had a look at Surefire and I think it should be
fairly easy to mimic the surefire plugin's behaviour but tweak it so
that it uses the application classloader.
I hope to get back into it this PM and should have something today.
That would provide a harness to run them but we will need to write
the tests themselves. As you probably all know I don't think that
using samples is the right way to go about testing - samples are
about illustrating things, testing is about trying to break stuff and
that involves lots of edge cases and other things that you don't want
to encourage users to do.
The rough idea I have is that we write the test cases as simple SCA
apps that run in a composite embedded in the maven process. These can
connect to the composites under test using SCA wiring - either in-
process for simple tests, or using bindings to connect to ones
running in a different (server) environment. Something like:
class HelloITest extends TestCase {
private HelloService service;
public testHello() {
assertEquals("Hello", service.getGreeting());
}
protected void setUp() {
super.setUp();
service = CurrentCompositeContext.locateService("HelloService");
}
}
--
Jeremy
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
