Ok, given the below and where the tests actually are now, I think it makes sense to drop the cpp profile support.
Robbie On 4 April 2017 at 12:06, Oleksandr Rudyy <oru...@gmail.com> wrote: > Hi Robbie, > > I am sorry, I meant to send the email into users list but somehow managed > to sent it into dev :(. > > Here are our current intentions regarding system tests: > * for new system tests (whether it is AMQP 0.x or AMQP 1.0) we would like > to use AMQP management to create/change/delete pre-required entities on > broker > * in short term we are not going to delete or refactor existing tests > * in long term we would like to sort out our system tests and leave only > sensible tests there > * it is unclear yet what we would be doing with JMS client tests, but, > IMHO, the system tests which are testing the client aspects only would need > to be moved into client source tree. Existing system tests are testing both > broker and client. Thus, it is difficult to separate them. We are not > planning any work in this area at the moment. The main development efforts > are concentrated on producing 7.0 release. The tests are changed on the > best effort basis: if there is an issue within the broker or tests itself > we try to fix it > * our main priority now is to make system tests running using AMQP 1.0 > protocol without "boiling the ocean". > > Regarding running tests against cpp broker: In my personal opinion we need > to have such tests in client source tree and broker source tree should only > contain java broker specific tests. > > Kind Regards, > Alex > > > On 3 April 2017 at 17:46, Robbie Gemmell <robbie.gemm...@gmail.com> wrote: > >> I wasn't around at the time and missed this among the deluge of >> backlogged mails when I returned. You might have had more luck using >> the users list given thats where most discussions are and theres less >> traffic to drown things out. >> >> Can you clarify some things for me. You mention wanting to use AMQP >> Management for AMQP 1.0 tests, but then later note specifically the >> Java broker supports it for 0-x too. Do you also wan't/plan to use it >> for 0-x tests as well? Do you plan to [re]move any tests that are >> mainly covering the client, since the system tests module has >> historicaly been for the combination of both rather than just the >> broker? >> >> Robbie >> >> On 3 April 2017 at 12:28, Oleksandr Rudyy <oru...@gmail.com> wrote: >> > Hi all, >> > >> > Since nobody sent any reply on my previous email I would like to re-ask >> > again whether there is any interest in running java broker system tests >> > against cpp broker? >> > >> > If there is no interest, we would like to remove the support for running >> > cpp broker with java broker system tests. >> > >> > Kind Regards, >> > Alex >> > >> > >> > On 20 March 2017 at 10:05, Oleksandr Rudyy <oru...@gmail.com> wrote: >> > >> >> Hi everybody, >> >> >> >> The existing system tests for java broker can be run against cpp >> >> broker (with some exceptions for the tests relying on java broker REST >> >> API or java broker specific features). >> >> >> >> Is there an interest to continue support of cpp broker in java broker >> >> system tests? >> >> >> >> The reasons behind this question are the following: >> >> 1) we want reduce the maintenance efforts for the tests >> >> 2) we want to use AMQP management for AMQP 1.0 in the system tests to >> >> create/delete/update configured entities on the broker but cpp broker >> >> does not support AMQP management whilst java broker supports it for >> >> both AMQP 1.0 and AMQP 0.x >> >> >> >> Kind Regards, >> >> Alex >> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org >> For additional commands, e-mail: dev-h...@qpid.apache.org >> >> --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
