On Wed, 2012-07-25 at 12:50 -0400, Joseph Ottinger wrote: > Well, as far as I could tell, there *are* no tests yet - which worries > me. But that's part of what motivated my desire to move to Maven; we > can configure Arquillian to crank up a Qpid instance so that we can > run tests as part of the build without too much fuss. > > And sure, if there're any things we need to confirm are working as > desired before we cut over, if we cut over, I have no problem putting > those in place at all.
There are no tests in the proton/proton-j sub-directory, however there are quite a few tests under proton/tests. These are written in python so that they can be run against both the Java (via jython) and C implementations (via the python bindings) and ensure consistent behavior between the two. If possible we'd actually like to keep all the tests in python in order to maximize both coverage and consistency between the two implementations. --Rafael --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
