Hello, Girish Vasmatkar <girish.vasmat...@hotwaxsystems.com> writes:
> Thanks Bilgin for taking care of pull request. If everyone is okay with the > changes, I will go ahead and create a ticket for the same to add it as an > ofbiz plugin. Let me know of any issues or concerns anyone may have. > > While writing a few test cases for the various camel components (and I am > using CamelTestSupport), it turned out OFBiz test container does not pick > them up because it is still based on inheritance (extending TestCase) and > not on annotation (any class with @Test annotated methods). I will probably > elaborate further in a separate thread, but I feel we need to add support > for considering such classes as part of test suite as well. We are using > JUnit 4 but it is hardly being used except for being available on the > classpath. Using JUnit 4 classes will make sure both mechanisms will be > supported. Supporting the JUnit4 runner API which make use of annotations would be nice if it helps improving the *sad* state of OFBiz integration tests in term of error reporting. For the record Junit4 annotations are already supported by OFBiz unit tests run by ‘./gradlew test’ which by the way should be preferred over integration tests in most cases because they run faster. As a side note, please avoid cross-posting to ‘devel’ and ‘user’ mailing lists. Thanks. -- Mathieu Lirzin GPG: F2A3 8D7E EB2B 6640 5761 070D 0ADE E100 9460 4D37
