Hope this helps.... You should never forget that under the hood Pax Exam will create a bundle called probe, that contains all your tests. That means that if your tests extend a class that is not present in the current module, it won't be found by your probe bundle. In older versions of Pax Exam you could pretty easily modify the contests of the probe and include additional classes from any module visible to your project. In the 2.x series its more complicated.
The easiest way to go is to make sure your install the bundle that contains the super class to the target container. http://iocanel.blogspot.com/2012/03/how-to-deal-with-common-problems-in-pax.html On Aug 23, 2013, at 12:05 PM, sankar wrote: > Hello, > > When I run an integration test via pax exam, it seems that the test probe is > only the **TestIntegration > class and not the rest of test classes (included in same or different file, > it does not matter). > > As a workaround, I add the test class logic in source code but this is a > temporary solution. > > Could you please advice on a better solution?Is there a way at all? > Thank you > > extra info : > karaf 2.3.1 > pax exam 2.6.0 > scala code > > > > > -- > View this message in context: > http://karaf.922171.n3.nabble.com/Cannot-refer-to-test-classes-from-a-TestIntegration-class-karaf-pax-exam-tp4029539.html > Sent from the Karaf - User mailing list archive at Nabble.com.
