[
https://issues.apache.org/jira/browse/QPID-1421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robbie Gemmell closed QPID-1421.
--------------------------------
Resolution: Won't Fix
> QMan Integration Tests : Tests with QMan & QPID running
> --------------------------------------------------------
>
> Key: QPID-1421
> URL: https://issues.apache.org/jira/browse/QPID-1421
> Project: Qpid
> Issue Type: Improvement
> Components: Java Tools
> Affects Versions: M4
> Environment: J2SE 5.0 or higher
> Reporter: Andrea Gazzarini
> Attachments: qman_systest_05112008.patch
>
>
> Actual bundle of QMan has only "offline" unit test that are running tests
> again isolated "components" of QMan.
> That means that in order to see those tests running you don't need to have
> QMan and / or Qpid running.
> This is good for development stage, allowing a (moreless) test-driven
> development and therefore a flexible code but in order to see that all is
> working (Test --> QMan --> Qpid) we need to add tests against a runnning QMan
> connected to a broker.
> I'm thinking about that...I already coded some tests but it's an hard work
> because the asynchronous nature of the interaction between QMan & Qpid.
> Probably QMan will be extended to support JMX notifications.
> I'm thinkng about that so I'm not sure but from a test perspective should be
> cool if you could register a test as a listener of QMan notifications and in
> that way you will be informed about object creations, events, method
> invocations and all what you need to run your verifications.
> If you some kind of idea feel free to suggest...
> Regards,
> Andrea
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
