OpenDaylight Summit 2016

I'd like to share some ongoing work I'm doing to write tests in netvirt's aclservice-impl & elanmanager-impl in a new "end2end" test style for offset 2 functional modules, at least some of which lack tests of real value IMHO (this effort does not target offset 0/offset 1 infrastructure framework projects). The approach in this style is pure Java JUnit, pure standalone Java (non-OSGi; so not really like a full-blown IT, as it's often not really needed IMHO), and non-CSIT. These tests should focus on simple testing of your bundles' API and their expected effect / outcome on the system, not their internal implementation details. Some of the dependant services in other modules are typically stubbed. Mocking is fairly limited or avoided all together. The internal beans of one bundle are all used together however. This is much more than your typical unit test, as those would, in theory at least, test each internal class separately; and use mocking, sometimes perhaps too extensively. Wiring of all bundle internal beans is through post-BP @Inject (successfully explored in netvirt), discussed in more details in another session. Conceptually this kind of test style is thus positioned between unit tests and IT/CSIT. Interested in feedback from attendees if they think this is worthwhile pursuing in general (not limited to netvirt), and see if this inspires you to use the same approach in your projects, or hear your objections. Session may include some live coding. It would also be good to agree on a name for this style (other than my only tentative "end2end" convention).