Manu, You are missing the whole point here. Just because we copy a file in our tests, they don't become integration tests. Can you tell me what an integration test from your understanding?
We do not need to copy files and hard-code OSGi bundles once this Pax Exam container for Carbon 5 is available. On Fri, May 13, 2016 at 10:48 PM, Manuranga Perera <[email protected]> wrote: > Hi Dharshana, > >> Avoid product teams to overuse containers to make it to the integration >> level. > > PAX is already at integration level. You can see the kernel team is coping > yaml files in PAX tests. This means they not unit tests. > > [1] > https://github.com/wso2/carbon-kernel/blob/master/tests/osgi-tests/src/test/java/org/wso2/carbon/osgi/runtime/CarbonRuntimeOSGiTest.java#L120 > -- > With regards, > *Manu*ranga Perera. > > phone : 071 7 70 20 50 > mail : [email protected] > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- Sameera Jayasoma, Software Architect, WSO2, Inc. (http://wso2.com) email: [email protected] blog: http://blog.sameera.org twitter: https://twitter.com/sameerajayasoma flickr: http://www.flickr.com/photos/sameera-jayasoma/collections Mobile: 0094776364456 Lean . Enterprise . Middleware
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
