Messaging Toolkit Test Plan Draft

JMS Operators

Supported Platforms:

• RHEL 5, RHEL 6, PPC, SLES

Supported Messaging Servers:

• (OK) Active MQ 5.7
• (pending test) Active MQ 5.9
• (OK) Websphere MQ 7.5.x
• (OK) Websphere MQ 8.0

Test Details

Connection Document

1. (OK) All supported data types from connection document schema (covered by automated tests)
2. (OK) All supported message class from connection document schema (covered by automated tests)
3. (OK) delivery mode: persistent vs non_persistent
4. connection document providing user name and password - pending configuration of activemq and wmq servers
5. Error conditions on connection documents:

• connection specification
  • no connection spec
  • connection specification pointing to provide_url that does not exist
  • connection specification providing incorrect user name and password
  • connection document is malformed
• access specification
  • no access specification
  • access specification providing incorrect identify as destination
  • access specification providing an invalid message class
  • access specification providing an invalid delivery mode
  • access specification providing an invalid connection
  • access specification providing no attribute on native schema
  • access specification providing invalid attribute type

Connection and Reconnection Policy

• reconnectionPolicy, reconnectionBound, period
• initial connection made, but connection dropped
• initial connection cannot be made, but is later available

Parameters

• required parameter not specified
• invalid connection specified
• invalid access specified
• default lookup of connection document
• specify connection document from non-default location (absolute and relative paths) - covered by automated test

XMS Operators

Supported Platforms:

• RHEL 5, RHEL 6, SLES

Supported Messaging Servers:

• Websphere MQ 7.5.x, Websphere MQ 8.0 (pending test)

Test Details

Connection Document

1. All supported data types from connection document schema (covered by automated tests)
2. All supported message class from connection document schema (covered by automated tests)
3. delivery mode: persistent vs non_persistent
4. connection document providing user name and password - only applicable for Websphere MQ 8.0
5. Error conditions on connection documents:

• connection specification
  • no connection spec
  • connection specification pointing to provide_url that does not exist
  • connection specification providing incorrect user name and password
  • connection document is malformed
• access specification
  • no access specification
  • access specification providing incorrect identify as destination
  • access specification providing an invalid message class
  • access specification providing an invalid delivery mode
  • access specification providing an invalid connection
  • access specification providing no attribute on native schema
  • access specification providing invalid attribute type

Connection and Reconnection Policy

• reconnectionPolicy, reconnectionBound, period
• initial connection made, but connection dropped
• initial connection cannot be made, but is later available

Parameters

• required parameter not specified
• invalid connection specified
• invalid access specified
• default lookup of connection document
• specify connection document from non-default location (absolute and relative paths) - covered by automated test

Kafka Operators

MQTT Operators