Marnie McCormack wrote:
How do we currently test that for various operations (like Session close)
the correct messages are dispatched i.e. so we avoid this case where the
close-ok didn't go ?
That was really what I was driving at on the test - obv we can stress
test/profile on a one off basis outside of the codebase/
I haven't followed the details of this Jira, but I would say that in
general these sorts of protocol operations effect state changes in some
entity, e.g. the session and/or the conection, and we should test that
the state change has occurred. This probably involves testing against
the implementing class(es) directly as the JMS interface may not expose
the accessors necessary to verify that the state change has occurred.
--Rafael
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
