[ 
https://issues.apache.org/jira/browse/QPIDIT-65?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16324203#comment-16324203
 ] 

Kim van der Riet commented on QPIDIT-65:
----------------------------------------

Add {{\-\-include-hdr}} and {{\-\-exclude-hdr}} to control headers in test.
Add {{\-\-include-prop}} and {\-\-exclude-prop}} to control properties in test.
Allow the exclude options to use the value {{ALL}} to exclude all headers or 
properties.

Currently each value runs as a single test, this is making the test very long 
and inefficient.
For headers, figure out a way to combine the values for each header into a 
single test running multiple messages, one message per value.
Where headers are combined, a single test containing messages with the cross 
product of the values of the headers should work.

> Add command-line controls to JMS_hdrs_props_test to control test more 
> precisely
> -------------------------------------------------------------------------------
>
>                 Key: QPIDIT-65
>                 URL: https://issues.apache.org/jira/browse/QPIDIT-65
>             Project: Apache QPID Interoperability Test Suite
>          Issue Type: Improvement
>          Components: JMS Headers and Properties Test
>    Affects Versions: 0.1.0
>            Reporter: Kim van der Riet
>            Assignee: Kim van der Riet
>            Priority: Minor
>
> The JMS hdrs_props_test needs additional command-line parameters to control 
> the test precisely. Since the test by default uses only the JMS_MESSAGE_TYPE 
> for this test, the --{include, exclude}-type paramter has no effect at 
> present, but should be used to change/modify the base message type. In 
> addition, a parameter switching on/off the headers and parameters is needed, 
> also a control for the type of header and type of parameters used.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to