Yes +1 for moving to Kernel 5.2.0 based OSGI testing. IMO for IS 6.0-m2 release also we *must* move into kernel 5.2.0, if not typical way of starting the servers via pax-exam (kernel 5.1.0) will deprecate soon and again we have to put another effort to port them to kernel 5.2.0.
WDYT? Thanks, Gayan On Thu, Feb 2, 2017 at 9:42 PM, Omindu Rathnaweera <[email protected]> wrote: > +1 for moving to 5.2.0 based OSGi testing. As per Chanka, it won't require > a lot of effort to migrate the existing OSGi tests to 5.2.0. Also in the > developer perspective, it will be much easier to write the tests since we > don't have to include each required dependency as PAX configuration options. > > Regards, > Omindu. > > On Thu, Feb 2, 2017 at 4:44 PM, KasunG Gajasinghe <[email protected]> wrote: > >> Hi Gayan, >> >> In Kernel 5.2.0, starting the servers by providing the distribution pack >> is coming. But this support is not sufficient in 5.1.0 that we are using. >> Until, then we can write our typical way of starting the servers via >> pax-exam for testing. >> >> Please note that even though we are exposing MSF4J, MSF4J services in IS >> are registered and discovered via OSGi. This is in contrast to pure java >> mode based tests in MSF4J. So, writing tests for a server started via >> Pax-exam is not an issue IMO. >> >> >> On Thu, Jan 26, 2017 at 11:01 PM, Gayan Gunawardana <[email protected]> >> wrote: >> >>> Hi All, >>> >>> We are in the process of writing test cases for repository [1]. This is >>> bit different than other repositories where we have OSGI tests. For SCIM we >>> have to test micro services exposed by SCIM provider component[2]. We are >>> planning to go with same approach as in ms4j test cases [3]. >>> >>> According to off-line discussion had with DharshanaW, service runtime >>> can be generated by running[4] as a server which includes >>> carbon-kernel+SCIM feature+dependent features for SCIM feature. >>> >>> Appreciate your feedback and suggestions if you have any concerns >>> regarding above approach. >>> >>> [1] https://github.com/wso2-extensions/identity-inbound-provisio >>> ning-scim2 >>> [2] https://github.com/wso2-extensions/identity-inbound-provisio >>> ning-scim2/tree/master/components/org.wso2.carbon.identity.i >>> nbound.provisioning.scim2.provider >>> [3] https://github.com/wso2/msf4j/tree/master/core/src/test >>> [4] https://github.com/wso2-extensions/identity-inbound-provisio >>> ning-scim2/tree/master/tests/distribution >>> >>> Thanks, >>> Gayan >>> -- >>> Gayan Gunawardana >>> Software Engineer; WSO2 Inc.; http://wso2.com/ >>> Email: [email protected] >>> Mobile: +94 (71) 8020933 >>> >>> _______________________________________________ >>> Dev mailing list >>> [email protected] >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> >> *Kasun Gajasinghe*Associate Technical Lead, WSO2 Inc. >> email: kasung AT spamfree wso2.com >> linked-in: http://lk.linkedin.com/in/gajasinghe >> blog: http://kasunbg.org >> phone: +1 650-745-4499 <(650)%20745-4499>, 77 678 0813 >> >> >> _______________________________________________ >> Dev mailing list >> [email protected] >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > Omindu Rathnaweera > Software Engineer, WSO2 Inc. > Mobile: +94 771 197 211 <+94%2077%20119%207211> > -- Gayan Gunawardana Software Engineer; WSO2 Inc.; http://wso2.com/ Email: [email protected] Mobile: +94 (71) 8020933
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
