Versions Compared

Old Version 6

changes.mady.by.user Martin Ritchie

Saved on

compared with

New Version 7

changes.mady.by.user Martin Ritchie

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Add testing via the ManagementConsole

...

  1. Running Broker
  2. Connected Client
    Output:
    No Format
    <date> CON-1002 : Close
    Validation Steps:
  3. The CON ID is correct
  4. This must be the last CON message for the Connection
  5. It must be preceeded by a CON-1001 for this Connection

Channel

The Channel test suite validates that the follow log messages as specified in the Functional Specification.

...

testConnectionCloseViaManagement

...

Description:
When a connected client has its connection closed via the Management Console this will be logged as a CON-1002 message.
Input:

  1. Running Broker
  2. Connected Client
  3. Connection is closed via Management Console
    Output:
    No Format

...

  1. <date> CON-1002 : Close
    Validation Steps:
  2. The CON ID is correct
  3. This must be the last CON message for the Connection
  4. It must be preceeded by a CON-1001 for this Connection

Channel

The Channel test suite validates that the follow log messages as specified in the Functional Specification.

This suite of tests validate that the Channel messages occur correctly and according to the following format:

No Format

CHN-1001 : Create : Prefetch <count>
CHN-1002 : Flow <value>
CHN-1003 : Close

...

  1. Running Broker
  2. Connected Client
  3. Client then requests that the Channel is closed
    Output:
    No Format
    
<date> CHN-1003 : Close
    Validation Steps:
  4. The MST ID is correct
  5. This must be the last message logged for this Channel.

Queue

The Queue test suite validates that the follow log messages as specified in the Functional Specification.

This suite of tests validate that the Queue messages occur correctly and according to the following format:

No Format

...

QUE-1001 : Create : [AutoDelete] [Durable|Transient] [Priority:<levels>] [Owner:<name>]
QUE-1002 :

...

Deleted

...

testQueueCreatePersistent

...

Description:

...

Queue

The Queue test suite validates that the follow log messages as specified in the Functional Specification.

...

When a simple persistent queue is created then a QUE-1001 create message is expected to be logged.
Input:

  1. Running broker
  2. Persistent Queue is created from a client
    Output:
    No Format
    
<date> QUE-1001 : Create :

...

  1. Persistent Owner:<name>

...

  1.

...

  1.  Validation Steps:
  2. The QUE ID is correct
  3. The Peristent tag is present in the message
  4. The Owner is as expected
...
testQueueCreatePersistentAutoDelete
...
testQueueCreatePersistent
...
Description:
 When a simple an autodelete persistent queue is created then a QUE-1001 create message is expected to be logged.
 Input: 
  1. Running broker
  2. AutoDelete Persistent Queue is created from a client
     Output: 
     No Format
    <date> QUE-1001 : Create : AutoDelete Persistent Owner:<name>

     Validation Steps:
  3. The QUE ID is correct
  4. The Peristent tag is present in the message
  5. The Owner is as expected
...
testQueueCreatePersistentAutoDelete
...
  1. The AutoDelete tag is present in the message
...
testCreateQueuePersistentPriority
...
Description:
 When an autodelete a persistent queue is created with a priority level then a QUE-1001 create message is expected to be logged.
 Input: 
  1. Running broker
  2. AutoDelete Persistent Queue is created from a client with a priority level
     Output: 
     No Format
    <date> QUE-1001 : Create : AutoDeletePersistent PersistentPriority:<levels> Owner:<name>

     Validation Steps:
  3. The QUE ID is correct
  4. The Peristent tag is present in the message
  5. The Owner is as expected
  6. The AutoDelete tag is present in the message
...
testCreateQueuePersistentPriority
...
  1. Priority level is correctly set
...
testCreateQueuePersistentAutoDeletePriority
...
Description:
 When a an autodelete persistent queue is created with a priority level then a QUE-1001 create message is expected to be logged.
 Input: 
  1. Running broker
  2. An AutoDelete Persistent Queue is created from a client with a priority level
     Output: 
     No Format
    <date> QUE-1001 : Create : AutoDelete Persistent Priority:<levels> Owner:<name>

     Validation Steps:
  3. The QUE ID is correct
  4. The Peristent tag is present in the message
  5. The Owner is as expected
  6. The AutoDelete tag is present in the message
  7. The Priority level is correctly set
...
testCreateQueuePersistentAutoDeletePriority
...
testQueueCreateTransient
...
Description:
 When an autodelete persistent a simple transient queue is created with a priority level then a QUE-1001 create message is expected to be logged.
 Input: 
  1. Running broker
  2. An AutoDelete Persistent Transient Queue is created from a client with priority
     Output: 
     No Format
    <date> QUE-1001 : Create : AutoDelete Persistent Priority:<levels> Transient Owner:<name>

     Validation Steps:
  3. The QUE ID is correct
  4. The Peristent Transient tag is present in the message
  5. The Owner is as expected
  6. The AutoDelete tag is present in the message
  7. The Priority level is correctly set
...
testQueueCreateTransient
...
testQueueCreateTransientAutoDelete
...
Description:
 When a simple an autodelete transient queue is created then a QUE-1001 create message is expected to be logged.
 Input: 
  1. Running broker
  2. AutoDelete Transient Queue is created from a client
     Output: 
     No Format
    <date> QUE-1001 : Create : AutoDelete Transient Owner:<name>

     Validation Steps:
  3. The QUE ID is correct
  4. The Transient tag is present in the message
  5. The Owner is as expected
...
testQueueCreateTransientAutoDelete
...
  2. The AutoDelete tag is present in the message
...
testCreateQueueTransientPriority
...
Description:
 When an autodelete a transient queue is created with a priority level then a QUE-1001 create message is expected to be logged.
 Input: 
  1. Running broker
  2. AutoDelete Transient Queue is created from a client with a priority level
     Output: 
     No Format
    <date> QUE-1001 : Create : AutoDeleteTransient TransientPriority:<levels> Owner:<name>

     Validation Steps:
  3. The QUE ID is correct
  4. The Transient tag is present in the message
  5. The Owner is as expected
  6. The AutoDelete tag is present in the message
...
testCreateQueueTransientPriority
...
  1. Priority level is correctly set
...
testCreateQueueTransientAutoDeletePriority
...
Description:
 When a an autodelete transient queue is created with a priority level then a QUE-1001 create message is expected to be logged.
 Input: 
  1. Running broker
  2. An autodelete Transient Queue is created from a client with a priority level
     Output: 
     No Format
    <date> QUE-1001 : Create : AutoDelete Transient Priority:<levels> Owner:<name>

     Validation Steps:
  3. The QUE ID is correct
  4. The Transient tag is present in the message
  5. The Owner is as expectedis as expected
  6. The AutoDelete tag is present in the message
  7. The Priority level is correctly set
...
testCreateQueueTransientAutoDeletePriority
...
testCreateQueueTransientViaManagementConsole
...
Description:
 When an autodelete transient Queue creation is possible from the Management Console. When a queue is created with a priority level in this way then a QUE-1001 create message is expected to be logged.
 Input: 
  1. Running broker
  2. Connected Management Console
  3. Queue Created via Management ConsoleAn autodelete Transient Queue is created from a client with a priority level
     Output: 
     No Format
    <date> QUE-1001 : Create : AutoDelete Transient Priority:<levels> Owner:<name>

     Validation Steps:
  4. The QUE ID is correct
  5. The Transient tag is correct tags are present in the message 
  6. The Owner is as expected
  7. The AutoDelete tag is present in the message
  8. The Priority level is correctly setbased on the create options
testQueueDelete
Description:
 An explict QueueDelete request must result in a QUE-1002 Deleted message being logged. One way the queue This can be deleted is done via na an explict AMQP QueueDelete method.
 Input: 
...
  1. Running Broker
  2. Client creates a temporary queue then disconnectsthen disconnects
     Output: 
     No Format
    
<date> QUE-1002 : Deleted

     Validation Steps:
  3. The QUE ID is correct
...
testQueueDeleteViaManagementConsole
...
Description:
 The ManagementConsole can be used to delete a queue. When this is done a QUE-1002 Deleted message must be logged.
 Input: 
  1. Running Broker
  2. Queue created on the broker with no subscribers
  3. Management Console connected
  4. Queue is deleted via Management Console
     Output: 
     No Format
    <date> QUE-1002 : Deleted

     Validation Steps:
  5. The QUE ID is correct
...
This suite of tests validate that the Exchange messages occur correctly and according to the following formatcorrectly and according to the following format:
 No Format

EXH-1001 : Create : [Durable] Type:<value> Name:<value>
EXH-1002 : Deleted

...
testExchangeCreateDurable
...
Description:
 When a durable exchange is created an EXH-1001 message is logged with the Durable tag. This will be the first message from this exchange.
 Input: 
  1. Running broker
  2. Client requests a durable exchange be created.
     Output: 
     No Format
    
<date> EXH-1001 : Create : 
...
  1. Durable
...
  1.  Type:<value> Name:<value>

...
  1.  Validation Steps:
  2. The EXH ID is correct
  3. The Durable tag is present in the message
...
testExchangeCreate
...
testExchangeCreateDurable
...
Description:
 When a durable an exchange is created an EXH-1001 message is logged with the Durable tag. This will be the first message from this exchange.
 Input: 
  1. Running broker
  2. Client requests a durable an exchange be created.
     Output: 
     No Format
    <date> EXH-1001 : Create : Durable Type:<value> Name:<value>

     Validation Steps:
  3. The EXH ID is correct
  4. The Durable tag is present in the message
...
testExchangeCreate
...
testExchangeDelete
...
Description:
 When an exchange is created An Exchange can be deleted through an AMQP ExchangeDelete method. When this is successful an EXH-10011002 Delete message is will be logged. This will be the first last message from this exchange.
 Input: 
  1. Running broker
  2. A new Exchange has been created
  3. Client requests an that the new exchange be createddeleted.
     Output: 
     No Format
    <date> EXH-1002 : Deleted

     Validation Steps:
  4. The EXH ID is correct
  5. There is a corresponding EXH-1001 Create message logged.
Binding
The Binding test suite validates that the follow log messages as specified in the Functional Specification.
This suite of tests validate that the Binding messages occur correctly and according to the following format:
 No Format

BND-1001 : Create [: Arguments 
...
: <key=value>]
BND-1002 : Deleted

...
testBindingCreate
...
Description:
 The binding of a Queue and an Exchange is done via a Binding. When this Binding is created a BND-1001 Create messasge will be logged
...
testExchangeDelete
...
Description:
 An Exchange can be deleted through an AMQP ExchangeDelete method. When this is successful an EXH-1002 Delete message will be logged. This will be the last message from this exchange.
 Input: 
  1. Running broker
  2. A new Exchange has been created
  3. Broker
  4. New Client requests that a Queue is bound to a new exchangeClient requests that the new exchange be deleted.
     Output: 
     No Format
    <date> EXHBND-10021001 : DeletedCreate 

     Validation Steps:
  5. The EXH BND ID is correct
  6. There is a corresponding EXH-1001 Create message logged.
Binding
The Binding test suite validates that the follow log messages as specified in the Functional Specification.
...
  1. This will be the first message for the given binding
...
testBindingCreateWithArguments
...
Description:
 A Binding can be made with a set of arguments. When this occurs we logged the key,value pairs as part of the Binding log message. When the subscriber with a JMS Selector consumes from an exclusive queue such as a topic. The binding is made with the JMS Selector as an argument.
 Input: 
  1. Running Broker
  2. Java Client consumes from a topic with a JMS selector.
     Output: 
     No Format
    
<date> BND-1001 : Create 
...
  1. : Arguments : <key=value>
...
  1. 

...
  1.  Validation Steps:
  2. The BND ID is correct
  3. The JMS Selector argument is present in the message
  4. This will be the first message for the given binding
...
testBindingCreateViaManagementConsole
...
testBindingCreate
...
Description:
 The binding of a Queue and an Exchange is done via a Binding. When this Binding is created via the Management Console a BND-1001 Create messasge will be logged. 
 Input: 
  1. Running Broker
  2. Connected Management Console
  3. Use Management Console to perform bindingNew Client requests that a Queue is bound to a new exchange.
     Output: 
     No Format
    <date> BND-1001 : Create 

     Validation Steps:
  4. The BND ID is correct
  5. This will be the first message for the given binding
...
testBindingCreateWithArguments
...
testBindingDelete
...
Description:
 A Binding can be made with a set of arguments. When this occurs we logged the key,value pairs as part of the Binding log message. When the subscriber with a JMS Selector consumes from an exclusive queue such as a topic. The binding is made with the JMS Selector as an argument Bindings can be deleted so that a queue can be rebound with a different set of values.
 Input: 
  1. Running Broker
  2. AMQP UnBind Request is madeJava Client consumes from a topic with a JMS selector.
     Output: 
     No Format
    <date> BND-10011002 : Create : Arguments : <key=value>Deleted

     Validation Steps:
  3. The BND ID is correctThe JMS Selector argument is present in the message
  4. There must have been a BND-1001 Create message first.
  5. This will be the first last message for the given binding
...
testBindingDelete
...
testBindingDeleteViaManagementConsole
...
Description:
 Bindings can be deleted so that a queue can be rebound with a different set of values. This can be performed via the Management Console
 Input: 
  1. Running Broker
  2. Management Console connected
  3. Management Console is used to perform unbind.AMQP UnBind Request is made
     Output: 
     No Format
    <date> BND-1002 : Deleted

     Validation Steps:
  4. The BND ID is correct
  5. There must have been a BND-1001 Create message first.
  6. This will be the last message for the given binding
...