Currently there are 2 tests, cpp and java/jms, in respective source trees. qpid/cpp/src/tests/qpid-cpp-benchmark qpid/java/tools/bin/qpid-jms-benchmark
Both tests use similar options (with a couple of exceptions). They also share majority of code, the exceptions are calls to qpid-send, qpid-receive and few other minor differences. There is a desire to provide one interface for all language implementations (as well as, extend implementation to other language clients). This goal can be accomplished in different ways: Option 1: Add a thin layer (new test) to check language preference and pass control to the corresponding test. In this case existing tests are preserved and continue to exist in the language specific source trees. The disadvantage is that we end up maintaining similar code in multiple places. Option 2: Consolidate tests into one source and place it in qpid/tests/src/py/qpid_tests/client/ location. The advantage is reduced maintenance, the disadvantage is that now one needs all qpid source to run a specific test. My recommendation is to proceed with Option 2 based on reduced maintenance. I will appreciate community feedback regarding this proposal. Regards, Irina. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
