Page History

Test ID

Test Steps

Expected Result

USER-0

Select the UserManagement node in the Qpid Connections tree.

The LoggingManagement MBean is opened in the MBean view

USER-1

Click the Add New User button

The Add New User dialog opens

USER-1.1

Enter Username=guest1, Password=guest1 and select Read Only access rights, then click ok.

guest1 will be added to the password and management rights files with indicated password and rights, and be added to the table with Read Only access rights.
NOTE: Verify that the password file and access rights files configured in the server configuration were updated.

USER-2

Select guest1 in the Users table and click the Set Rights button,

The Set Rights dialog opens

USER-2.1

Select Admin rights and press ok.

guest1 rights in the management rights files will be changed to admin, and it will be displayed in the table with Admin rights.
NOTE: Verify that the access rights file configured in the server configuration was updated.

USER-3

Select guest1 in the Users table and click the Set Password button,

The Set Password dialog opens

USER-3.1

Enter Password=newpass and press ok.

guest1 will altered to have password newpass in the password file. There will be no visible change in the table.
NOTE: Verify that the password file configured in the server configuration was updated.

USER-4

Select guest1 in the Users table and click the Delete Users(S) button, then validate the operation when prompted for confirmation.

guest1 will be removed from the password file and rights file and disappear from the table.
NOTE: Verify that the password file and access rights files configured in the server configuration were updated.

USER-5

Repeat USER-1 &1.1

As USER-1.1

USER-6

Repeat USER-1 & 1.1 with Username=client1, Password=client1 and select No Access rights.

As USER-1.1 but with the new credentials, and the rights file will not be modified.

USER-7

Alter the password file on disk to add user1:user1, and alter the access rights file on disk to add user1=readwrite.

No change. The password and rights files are only read once at startup by the server, until instructed to reload them via JMX.

USER-8.1

Press the Reload User Data button

user1 will be added to the server and shown in the table with Read & Write access rights.
(Older servers only reload the rights file, and so no change in the table will be visible in this case)

USER-8

Select the <hostname>:8999 node in the Qpid Connections tree and then click the Disconnect button in the toolbar

The connection is closed and the <hostname>:8999 tree node collapses to a single entry.

USER-8.1

Select the <hostname>:8999 node in the Qpid Connections tree and then click the "Reconnect" icon

The Reconnect dialog opens

USER-8.2

Enter Username=guest1user1, Password=guest1 user1 and then click Connect.

The server node will be expanded to show the ServerInformation MBean as well as a VirtualHosts folder containing child folders development, localhost, and test.
The ConfigurationManagement, LoggingManagement, and UserManagement MBeans will not be shown as only admin-level users have access to these.

USER-9

Select the <hostname>:8999 node in the Qpid Connections tree and then click the Disconnect button in the toolbar

The connection is closed and the <hostname>:8999 tree node collapses to a single entry.

USER-9.1

Select the <hostname>:8999 node in the Qpid Connections tree and then click the "Reconnect" icon

The Reconnect dialog opens

USER-9.2

Enter Username=client1, Password=client1 and click Connect.

The connection attempt fails, as user client1 has no management access rights.

Test ID

Test Steps

Expected Result

QUEUE-0

Select the Queues node for the test VirtualHost in the Qpid Connections tree.

The Queue selection screen is opened in the MBean view, listing Queues ping,ping_1, and queue in the table.

QUEUE-1

Press the SelectAttributes button.

The Select Attributes dialog opens.

QUEUE-1.1

Select additional Ensure the following attributes re ConsumerCount, Durable, MessageCount, QueueDepth and then press OK.

The table updates to show additional columns for the new Attributes. All queues have additional attribute values of 0, false, 0, and 0bytes.

QUEUE-2

Run the ping_sender.sh utility script, but do not press a key to exit the script when the sending is complete.

100 messages of size 512bytes are sent to the ping_1 queue. After a refresh interval elapses, the table updates to show ping_1 having 100 messages and a queue depth of 50.000 KB, as well as a new queue named TempQueue<etc>.

QUEUE-2.1

Press a key in the script shell to make it exit.

After another refresh interval elapses, the table will update to show the TempQueue has been deleted.

QUEUE-3

Select queue ping_1 in the table and click the Add Queue(s) to favourites button, then click the + icon at the Queues node to expand the Queues node.

ping_1 has been added as a child node of Queues.

QUEUE-3.1

Select the new ping_1 node in the Qpid Connections tree.

The ping_1 queue MBean opens in the MBean View, showing the Attributes tab.

QUEUE-3.2

Select the Operations tab in the ping_1 MBean view.

The Operations tab opens, with the details of the first 50 messages on ping_1 visible in the table.

Test ID

Test Steps

Expected Result

QUEUE-8

Select the messages with AMQ IDs 11,13-14,19-20 (Note that since 0.6 the IDs now start at 2 and so the IDs here will be n+1.)and press the Move Message(s) button_._

The Move Messages dialog opens, requesting destination queue and confirmation of moving messages with AMQ ID 11,13-14,19-20.

QUEUE-8.1

Press OK (using the ping destination already selected).

The messages with AMQ IDs 11,13-14,19-20 are moved and disappear from the table, which now shows messages AMQ ID 12,15-18, and 21-25.

QUEUE-9

Select the messages with AMQ IDs 12,15-18 and press the Copy Message(s) button_._

The Copy Messages dialog opens, requesting destination queue and confirmation of moving messages with AMQ IDs 12,15-18.

QUEUE-9.1

Select the queue as the destination queue Press OK.

The messages are copied, as indicated in the status bar at the bottom left of the application, and they continue to be present on the ping_1 queue.

QUEUE-10

The messages with AMQ IDs 12,15-18 are still selected. Press the Delete Message(s) button and confirm the prompt_._

The messages with AMQ IDs 12,15-18 are deleted and disappear from the table, which now shows messages with AMQ ID 21-30 in positions 11-20.

QUEUE-11

Press the Clear Queue button and confirm the prompt.

The queue is cleared of the 90 remaining (and unacquired) messages and the table becomes empty.
Note: The number of deleted unacquired messages is reported in the status bar only for newer brokers

Test ID

Test Steps

Expected Result

EXCH-0

Select the Exchanges node for the test VirtualHost in the Qpid Connections tree.

The Exchanges selection screen is opened in the MBean view, listing Exchanges <<default>>, amq.direct, amq.fanout, amq.match, and amq.topic in the table.

EXCH-0.1

Select exchanges amq.direct and amq.match ping_1 in the table and click the Add Exchanges(s) to favourites button, then click the + icon at the Exchanges node to expand the Exchanges node.

amq.direct and amq.match have been added as a child nodes of Exchanges.

EXCH-1

Select the new amq.direct node in the Qpid Connections tree.

The amq.direct exchange MBean opens in the MBean View, showing the Attributes tab.

EXCH-1.1

Select the Operations tab in the amq.direct MBean view.

The Operations tab opens

EXCH-2

Select the ping entry in the Binding Key table.

The Queue Names table updates and shows the ping queue is associated with the selected binding.

EXCH-4

Select the amq.match node in the Qpid Connections tree.

The amq.match exchange MBean opens in the MBean View, showing the Attributes tab.

EXCH-4.1

Select the Operations tab in the amq.match MBean view.

The Operations tab opens. The Binding Number and QueueName table is empty.

EXCH -4.2

Select the amq.match node in the Qpid Connections tree.

The amq.match exchange MBean opens in the MBean View, showing the Attributes tab.

EXCH-4.3

Select the Operations tab in the amq.match MBean view.

The Operations tab opens. The Binding Number and QueueName table is empty.

EXCH -5

Press the Create button at the right hand side of the Bindings group.

The Create New Binding dialog opens.

EXCH-5.1

Select a value of 'all' for the x-match key. Then enter a new key called key1, with a value of value1, and a new key called key2 with a value of value2. Press the Add additional field button, and a new empty row should be added at the bottom, giving 4 3 empty rows. Press OK.

The binding is created and an entry added to the table with Binding Number 1 and Queue Name ping.

EXCH-5.2

Select the binding entry in the table.

The Header Bindings table should update to list the keys and values entered in the dialog:
key1=value1
key2=value2
x-match=any