[
https://issues.apache.org/jira/browse/QPIDIT-20?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kim van der Riet resolved QPIDIT-20.
------------------------------------
Resolution: Fixed
Added:
* A small broker client which extracts the connection properties, and from
which the broker product name may be obtained;
* A BROKER_SKIP map which maps test types (AMQP types or JMS message types) to
broker names (as returned by the broker connection properties). If such a
mapping is found to exist, then the test for that type is skipped.
> Add ability to detect broker, skip tests that fail for that broker
> ------------------------------------------------------------------
>
> Key: QPIDIT-20
> URL: https://issues.apache.org/jira/browse/QPIDIT-20
> Project: Apache QPID IT
> Issue Type: Improvement
> Components: JmsMessageTest, SimpleTypeTest
> Reporter: Kim van der Riet
> Assignee: Kim van der Riet
>
> The Qpid broker will not handle some AMQP types correctly, and will attempt
> to read the body of these types as descriptors. This bug covered elsewhere.
> However, this issue causes the AMQP tests using these types to fail when the
> Qpid broker is in use. However, the A-MQ broker works ok.
> Until now, the types that do not work have had to be commented out of the
> test before running it in order to complete the test when using Qpid as the
> broker. This is ugly and error-prone, and certainly does not lend itself to
> automatic testing environments.
> A method needs to be devised that can detect the broker in use, and
> automatically exclude or skip tests that are known to fail with an
> appropriate message.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
