Hi, Amindri. Test cases are usually self-contained. They will be run as part of the maven build to verify certain functions are working. In your case, we can use the Tuscany API to start Tuscany runtime and a composite application. You can mimic the following test case:
https://svn.apache.org/repos/asf/tuscany/sca-java-2.x/trunk/testing/itest/services/src/test/java/org/apache/tuscany/sca/itest/services/ServicesTestCase.java Please note the @BeforeClass annotated method will bootstrap Tuscany (starting a node). You can add any test methods (@Test) to talk to JMX to verify the features. Thanks, Raymond On Sat, Aug 20, 2011 at 8:16 AM, Amindri Udugala <[email protected]>wrote: > And aabout the test case. The jmx module activator needs tuscany to run > continuously. So I will write the test case assuming that tuscany is already > bootstrapped. > > On 20 August 2011 17:43, Amindri Udugala <[email protected]> wrote: > >> Hi Raymond, >> >> Now everything is up and running. Bellow I have listed the artifacts I'm >> monitoring. Is there any thing that I have missed out? >> >> 1. Composites >> 2. Components >> 3. ComponentServices >> 4. Endpoints >> 5. EndpointReferences >> 6. RuntimeWireProcessors >> 7. ProviderFactoryExtensionPoint >> 8. DefaultWirePeocessorExtensionPoint >> > > > > -- > Thanks > > Amindri Udugala > University of Colombo School of Computing, > Sri Lanka. > >
