Versions Compared

Old Version 7

changes.mady.by.user Gordon Sim

Saved on

compared with

New Version 8

changes.mady.by.user Rupert Smith

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Draft.

Rupert Smith.

22nd Feb 2007

Document started.

Working Copy.

Rupert Smith.

6th Mar 2007

Document updated from feedback to draft on qpid-dev list. Last requirement # used: 47

Working Copy.

Rupert Smith.

7th Mar 2007

Senders and receivers to send reports to coordinator. Reply-to added to broadcast messages. Last requirement # used: 49

Working Copy.

Rupert Smith.

13th Mar 2007

Added test case names. Last requirement # used: 52

Working Copy.

Rupert Smith.

25th Spet 2007

Added test cases for message size variation. Last requirement # used: 60

Introduction:

The requirements in this specification use a common format, an example of which is given below:

...

IOP-44.

Basic P2P Setup.

Prior to assigning roles, the coordinator will bind a queue to the default direct exchange with a routing key, the same as the queue name. It will create a fresh queue and key for every test case instance.

IOP-45.

Basic P2P Assign Role Parameters.

Section

In addition to the invite message format defined in IOP-26, the basic p2p test invite will also include the following parameters.

No Format
          "P2P_QUEUE_AND_KEY_NAME",     "<name>"
          "P2P_NUM_MESSAGES",           <count>  (signed 32 bit int), P2P_NUM_MESSAGES property.

IOP-51.

Test Case 1 2 Name.

The "TEST_NAME" field in the test invite (IOP-25) will be "TC2_BasicP2P" for this test.

...

IOP-46.

Basic Pub/Sub Setup.

Prior to assigning roles, the coordinator will choose a routing key for the test. If will create a fresh key for every test case instance.

IOP-47.

Basic Pub/Sub Invite Parameters.

Section

In addition to the invite message format defined in IOP-26, the basic pub/sub test invite will also include the following parameters.

No Format
          "PUBSUB_KEY",                  "<key>"
          "PUBSUB_NUM_RECEIVERS",        <count> (signed 32 bit int), PUBSUB_NUM_RECEIVERS property.
          "PUBSUB_NUM_MESSAGES",         <count> (signed 32 bit int), PUBSUB_NUM_MESSAGES property.

IOP-52.

Test Case 1 3 Name.

The "TEST_NAME" field in the test invite (IOP-25) will be "TC3_BasicPubSub" for this test.

Test Case 4. P2P Test with Different Message Sizes.

  • This test case uses requirements IOP-38 to 43 inclusive.

The sending client creates a fresh correlation id, and the entire test case conversation uses this id.
The sending client will send the required number of test messages to the test routing key on the default direct exchange.
The sending client will send a message count report to the coordinator.
In response to a status request from the coordinator, the receiving client will reply with a message count report.
The coordinator will compare the messages received to the messages sent and pass or fail the test accordingly.
The above test cycle will be repeated for each message size to test.

IOP-53.

P2P Message Size Test Setup.

Prior to assigning roles, the coordinator will bind a queue to the default direct exchange with a routing key, the same as the queue name. It will create a fresh queue and key for every test case instance.

IOP-54.

P2P Message Size Test Assign Role Parameters.

Section

In addition to the invite message format defined in IOP-26, the basic p2p test invite will also include the following parameters.

No Format

          "P2P_QUEUE_AND_KEY_NAME",     "<name>"
          "P2P_NUM_MESSAGES",           <count>  (signed 32 bit int), P2P_NUM_MESSAGES property.
          "messageSize",                <count>  (signed 32-bit int).

IOP-55.

P2P Message Size Test Sizes

The following values for the message size parameter will be tested: 0K, 63K, 64K, 65K, 127K, 128K, 129K, 255K, 256K, 257K.

IOP-56.

Test Case 4 Name.

The "TEST_NAME" field in the test invite (IOP-25) will be "TC4_P2PMessageSize" for this test.

Test Case 5. Pub/Sub Test with Different Message Sizes.

  • This test case uses requirements IOP-38 to 43 inclusive.

The sending client creates a fresh correlation id, and the entire test case conversation uses this id.
The sending client will send the required number of test messages to the test routing key on the default topic exchange.
The sending client will send a message count report to the coordinator.
In response to a status request from the coordinator, the receiving client will reply with a message count report. This number will be the number of messages sent multiplied by the number of receivers being simulated by the receiving client.
The coordinator will compare the messages received to the messages sent and pass or fail the test accordingly.
The above test cycle will be repeated for each message size to test.

IOP-57.

Pub/Sub Message Size Test Setup.

Prior to assigning roles, the coordinator will choose a routing key for the test. If will create a fresh key for every test case instance.

IOP-58.

Pub/Sub Message Size Test Invite Parameters.

Section

In addition to the invite message format defined in IOP-26, the basic pub/sub test invite will also include the following parameters.

No Format

          "PUBSUB_KEY",                 "<key>"
          "PUBSUB_NUM_RECEIVERS",       <count> (signed 32 bit int), PUBSUB_NUM_RECEIVERS property.
          "PUBSUB_NUM_MESSAGES",        <count> (signed 32 bit int), PUBSUB_NUM_MESSAGES property.
          "messageSize",                <count> (signed 32-bit int).

IOP-59.

P2P Message Size Test Sizes

The following values for the message size parameter will be tested: 0K, 63K, 64K, 65K, 127K, 128K, 129K, 255K, 256K, 257K.

IOP-60.

Test Case 5 Name.

The "TEST_NAME" field in the test invite (IOP-25) will be "TC5_PubSubMessageSize" for this test.

Waiting Room:

...