You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "William Henry (JIRA)" <qp...@incubator.apache.org> on 2008/09/24 18:06:44 UTC

[jira] Created: (QPID-1291) Test queueMoveMessages on the management interface.

Test queueMoveMessages on the management interface.
---------------------------------------------------

                 Key: QPID-1291
                 URL: https://issues.apache.org/jira/browse/QPID-1291
             Project: Qpid
          Issue Type: Test
          Components: Python Test Suite
    Affects Versions: M4
            Reporter: William Henry


This test will test the queueMoveMessages and therefore also test Broker::queueMoveMessages and Queue::move

It sets up a source queue and loads 20 messages on the queue using the direct exchange, It then sets up a destination queue.

It then tests that moving 10 messages from src-queue to dest-queue was successful by testing the return status of the call and the message depths of the respective queues - both should be 10. 

It then uses the '0' qty to see if that will result in ALL remaining messages being moved to dest-queue (expected behavior). It checks status and message depths. 

It then tests to see if a bad source queue name results in a Invalid Parameter status value 4) and then the same again for a bad destination queue. 

It then sees if passing a number larger than the current queue depth will result in all the messages being moved. IT does this by using the quantity 40 when attempting to move messages back from the destination queue to the source queue. It again tests the queue depth. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Assigned: (QPID-1291) Test queueMoveMessages on the management interface.

Posted by "Ted Ross (JIRA)" <qp...@incubator.apache.org>.
     [ https://issues.apache.org/jira/browse/QPID-1291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ted Ross reassigned QPID-1291:
------------------------------

    Assignee: Ted Ross

> Test queueMoveMessages on the management interface.
> ---------------------------------------------------
>
>                 Key: QPID-1291
>                 URL: https://issues.apache.org/jira/browse/QPID-1291
>             Project: Qpid
>          Issue Type: Test
>          Components: Python Test Suite
>    Affects Versions: M4
>            Reporter: William Henry
>            Assignee: Ted Ross
>         Attachments: test_movemessages_diff.txt
>
>
> This test will test the queueMoveMessages and therefore also test Broker::queueMoveMessages and Queue::move
> It sets up a source queue and loads 20 messages on the queue using the direct exchange, It then sets up a destination queue.
> It then tests that moving 10 messages from src-queue to dest-queue was successful by testing the return status of the call and the message depths of the respective queues - both should be 10. 
> It then uses the '0' qty to see if that will result in ALL remaining messages being moved to dest-queue (expected behavior). It checks status and message depths. 
> It then tests to see if a bad source queue name results in a Invalid Parameter status value 4) and then the same again for a bad destination queue. 
> It then sees if passing a number larger than the current queue depth will result in all the messages being moved. IT does this by using the quantity 40 when attempting to move messages back from the destination queue to the source queue. It again tests the queue depth. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (QPID-1291) Test queueMoveMessages on the management interface.

Posted by "Ted Ross (JIRA)" <qp...@incubator.apache.org>.
    [ https://issues.apache.org/jira/browse/QPID-1291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12634211#action_12634211 ] 

Ted Ross commented on QPID-1291:
--------------------------------

I've committed a modified version of William's patch.

Instead of requiring the individual test to set up a qmf-console session, I've added this capability to the test harness.  Now, any test that wishes to use QMF console must call "self.startQmf()" first, then reference the session through "self.qmf".  The session and broker connection will be automatically torn down at the end of the test.


> Test queueMoveMessages on the management interface.
> ---------------------------------------------------
>
>                 Key: QPID-1291
>                 URL: https://issues.apache.org/jira/browse/QPID-1291
>             Project: Qpid
>          Issue Type: Test
>          Components: Python Test Suite
>    Affects Versions: M4
>            Reporter: William Henry
>            Assignee: Ted Ross
>         Attachments: test_movemessages_diff.txt
>
>
> This test will test the queueMoveMessages and therefore also test Broker::queueMoveMessages and Queue::move
> It sets up a source queue and loads 20 messages on the queue using the direct exchange, It then sets up a destination queue.
> It then tests that moving 10 messages from src-queue to dest-queue was successful by testing the return status of the call and the message depths of the respective queues - both should be 10. 
> It then uses the '0' qty to see if that will result in ALL remaining messages being moved to dest-queue (expected behavior). It checks status and message depths. 
> It then tests to see if a bad source queue name results in a Invalid Parameter status value 4) and then the same again for a bad destination queue. 
> It then sees if passing a number larger than the current queue depth will result in all the messages being moved. IT does this by using the quantity 40 when attempting to move messages back from the destination queue to the source queue. It again tests the queue depth. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Issue Comment Edited: (QPID-1291) Test queueMoveMessages on the management interface.

Posted by "William Henry (JIRA)" <qp...@incubator.apache.org>.
    [ https://issues.apache.org/jira/browse/QPID-1291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12634186#action_12634186 ] 

whenry edited comment on QPID-1291 at 9/24/08 9:09 AM:
--------------------------------------------------------------

Python diff on qpid/python/tests_0-10/management.py

See https://issues.apache.org/jira/browse/QPID-1290 for the code that is being tested.

      was (Author: whenry):
    Python diff on qpid/python/tests_0-10/management.py
  
> Test queueMoveMessages on the management interface.
> ---------------------------------------------------
>
>                 Key: QPID-1291
>                 URL: https://issues.apache.org/jira/browse/QPID-1291
>             Project: Qpid
>          Issue Type: Test
>          Components: Python Test Suite
>    Affects Versions: M4
>            Reporter: William Henry
>         Attachments: test_movemessages_diff.txt
>
>
> This test will test the queueMoveMessages and therefore also test Broker::queueMoveMessages and Queue::move
> It sets up a source queue and loads 20 messages on the queue using the direct exchange, It then sets up a destination queue.
> It then tests that moving 10 messages from src-queue to dest-queue was successful by testing the return status of the call and the message depths of the respective queues - both should be 10. 
> It then uses the '0' qty to see if that will result in ALL remaining messages being moved to dest-queue (expected behavior). It checks status and message depths. 
> It then tests to see if a bad source queue name results in a Invalid Parameter status value 4) and then the same again for a bad destination queue. 
> It then sees if passing a number larger than the current queue depth will result in all the messages being moved. IT does this by using the quantity 40 when attempting to move messages back from the destination queue to the source queue. It again tests the queue depth. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Resolved: (QPID-1291) Test queueMoveMessages on the management interface.

Posted by "Ted Ross (JIRA)" <qp...@incubator.apache.org>.
     [ https://issues.apache.org/jira/browse/QPID-1291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ted Ross resolved QPID-1291.
----------------------------

       Resolution: Fixed
    Fix Version/s: M4

> Test queueMoveMessages on the management interface.
> ---------------------------------------------------
>
>                 Key: QPID-1291
>                 URL: https://issues.apache.org/jira/browse/QPID-1291
>             Project: Qpid
>          Issue Type: Test
>          Components: Python Test Suite
>    Affects Versions: M4
>            Reporter: William Henry
>            Assignee: Ted Ross
>             Fix For: M4
>
>         Attachments: test_movemessages_diff.txt
>
>
> This test will test the queueMoveMessages and therefore also test Broker::queueMoveMessages and Queue::move
> It sets up a source queue and loads 20 messages on the queue using the direct exchange, It then sets up a destination queue.
> It then tests that moving 10 messages from src-queue to dest-queue was successful by testing the return status of the call and the message depths of the respective queues - both should be 10. 
> It then uses the '0' qty to see if that will result in ALL remaining messages being moved to dest-queue (expected behavior). It checks status and message depths. 
> It then tests to see if a bad source queue name results in a Invalid Parameter status value 4) and then the same again for a bad destination queue. 
> It then sees if passing a number larger than the current queue depth will result in all the messages being moved. IT does this by using the quantity 40 when attempting to move messages back from the destination queue to the source queue. It again tests the queue depth. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (QPID-1291) Test queueMoveMessages on the management interface.

Posted by "William Henry (JIRA)" <qp...@incubator.apache.org>.
    [ https://issues.apache.org/jira/browse/QPID-1291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12634301#action_12634301 ] 

William Henry commented on QPID-1291:
-------------------------------------

See also https://issues.apache.org/jira/browse/QPID-1292

> Test queueMoveMessages on the management interface.
> ---------------------------------------------------
>
>                 Key: QPID-1291
>                 URL: https://issues.apache.org/jira/browse/QPID-1291
>             Project: Qpid
>          Issue Type: Test
>          Components: Python Test Suite
>    Affects Versions: M4
>            Reporter: William Henry
>            Assignee: Ted Ross
>         Attachments: test_movemessages_diff.txt
>
>
> This test will test the queueMoveMessages and therefore also test Broker::queueMoveMessages and Queue::move
> It sets up a source queue and loads 20 messages on the queue using the direct exchange, It then sets up a destination queue.
> It then tests that moving 10 messages from src-queue to dest-queue was successful by testing the return status of the call and the message depths of the respective queues - both should be 10. 
> It then uses the '0' qty to see if that will result in ALL remaining messages being moved to dest-queue (expected behavior). It checks status and message depths. 
> It then tests to see if a bad source queue name results in a Invalid Parameter status value 4) and then the same again for a bad destination queue. 
> It then sees if passing a number larger than the current queue depth will result in all the messages being moved. IT does this by using the quantity 40 when attempting to move messages back from the destination queue to the source queue. It again tests the queue depth. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (QPID-1291) Test queueMoveMessages on the management interface.

Posted by "William Henry (JIRA)" <qp...@incubator.apache.org>.
     [ https://issues.apache.org/jira/browse/QPID-1291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

William Henry updated QPID-1291:
--------------------------------

    Attachment: test_movemessages_diff.txt

Python diff on qpid/python/tests_0-10/management.py

> Test queueMoveMessages on the management interface.
> ---------------------------------------------------
>
>                 Key: QPID-1291
>                 URL: https://issues.apache.org/jira/browse/QPID-1291
>             Project: Qpid
>          Issue Type: Test
>          Components: Python Test Suite
>    Affects Versions: M4
>            Reporter: William Henry
>         Attachments: test_movemessages_diff.txt
>
>
> This test will test the queueMoveMessages and therefore also test Broker::queueMoveMessages and Queue::move
> It sets up a source queue and loads 20 messages on the queue using the direct exchange, It then sets up a destination queue.
> It then tests that moving 10 messages from src-queue to dest-queue was successful by testing the return status of the call and the message depths of the respective queues - both should be 10. 
> It then uses the '0' qty to see if that will result in ALL remaining messages being moved to dest-queue (expected behavior). It checks status and message depths. 
> It then tests to see if a bad source queue name results in a Invalid Parameter status value 4) and then the same again for a bad destination queue. 
> It then sees if passing a number larger than the current queue depth will result in all the messages being moved. IT does this by using the quantity 40 when attempting to move messages back from the destination queue to the source queue. It again tests the queue depth. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.