Versions Compared

Old Version 5

changes.mady.by.user Martin Ritchie

Saved on

compared with

New Version 6

changes.mady.by.user Martin Ritchie

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

Wokring 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

Introduction:

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

...

The purpose of this test case is to check that clients can interoperate succesfully with the test coordinator and participate in the sequencing of the tests.

IOP-50.

Test Case 1 Name.

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

Test Case 2. Basic P2P Test.

...

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 Name.

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

Test Case 3. Basic Pub/Sub Test.

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

...

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 Name.

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

Waiting Room:

Contains ideas for possible future directions relating to this spec.

...