Qpid
  1. Qpid
  2. QPID-3775

Automate the manual persistent store tests

    Details

    • Type: Task Task
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 0.15
    • Component/s: Java Tests
    • Labels:
      None

      Description

      The Java broker currently has a suite of manual persistent store tests. These tests should be automated as part of the System Test suite.

      BDB-Qpid-1 Verifies that committed messages survive clean broker shutdown, after fully completing a number of transactions.
      BDB-Qpid-2 Verifies that committed messages survive immediate (kill -9) broker shutdown, after fully completing a number of transactions.
      BDB-Qpid-5 Verifies that committed messages survive clean broker shutdown, when broker is shutdown mid-transaction.
      BDB-Qpid-6 Verifies that committed messages survive immediate (kill -9) broker shutdown, when broker is shutdown mid-transaction.
      BDB-Qpid-7 Verifies that committed messages survive client connection termination, when clients connection is closed mid-transaction.
      BDB-Qpid-8 Verifies that committed messages survive message store backup and restore, when broker is restarted on a restored backup.

      The non-store implementation specific tests should be incorporated into the PersistentStoreTest system test. The test BDB-Qpid-8 is BDB specific and a should be implemented as in BDB specific system test.

      QBTC will need to be extended to permit the shutting down the Broker down ungracefully (using kill -9). Currently the framework uses java.lang.Process#destroy() which is implemented as kill -15.

        Activity

        Keith Wall created issue -
        Keith Wall made changes -
        Field Original Value New Value
        Assignee Keith Wall [ k-wall ]
        Keith Wall made changes -
        Attachment 0001-QPID-3775-Automate-the-manual-persistent-store-tests.patch [ 12511454 ]
        Keith Wall made changes -
        Description The Java broker currently has a suite of manual test. These tests should be automated as part of the System Test suite.

        BDB-Qpid-1 Verifies that committed messages survive clean broker shutdown, after fully completing a number of transactions.
        BDB-Qpid-2 Verifies that committed messages survive immediate (kill -9) broker shutdown, after fully completing a number of transactions.
        BDB-Qpid-5 Verifies that committed messages survive clean broker shutdown, when broker is shutdown mid-transaction.
        BDB-Qpid-6 Verifies that committed messages survive immediate (kill -9) broker shutdown, when broker is shutdown mid-transaction.
        BDB-Qpid-7 Verifies that committed messages survive client connection termination, when clients connection is closed mid-transaction.
        BDB-Qpid-8 Verifies that committed messages survive message store backup and restore, when broker is restarted on a restored backup.

        The non-store implementation specific tests should be incorporated into the PersistentStoreTest system test. The test BDB-Qpid-8 is BDB specific and a should be implemented as in BDB specific system test.

        QBTC will need to be extended to shut the Broker down gracefully (using kill -15). Currently the framework uses java.lang.Process#destroy() which is implemented as kill -9.
        The Java broker currently has a suite of manual persistent store tests. These tests should be automated as part of the System Test suite.

        BDB-Qpid-1 Verifies that committed messages survive clean broker shutdown, after fully completing a number of transactions.
        BDB-Qpid-2 Verifies that committed messages survive immediate (kill -9) broker shutdown, after fully completing a number of transactions.
        BDB-Qpid-5 Verifies that committed messages survive clean broker shutdown, when broker is shutdown mid-transaction.
        BDB-Qpid-6 Verifies that committed messages survive immediate (kill -9) broker shutdown, when broker is shutdown mid-transaction.
        BDB-Qpid-7 Verifies that committed messages survive client connection termination, when clients connection is closed mid-transaction.
        BDB-Qpid-8 Verifies that committed messages survive message store backup and restore, when broker is restarted on a restored backup.

        The non-store implementation specific tests should be incorporated into the PersistentStoreTest system test. The test BDB-Qpid-8 is BDB specific and a should be implemented as in BDB specific system test.

        QBTC will need to be extended to permit the shutting down the Broker down gracefully (using kill -15). Currently the framework uses java.lang.Process#destroy() which is implemented as kill -9.
        Keith Wall made changes -
        Attachment 0001-QPID-3775-Automate-the-manual-persistent-store-tests.patch [ 12511454 ]
        Keith Wall made changes -
        Alex Rudyy made changes -
        Assignee Keith Wall [ k-wall ] Alex Rudyy [ alex.rufous ]
        Alex Rudyy made changes -
        Status Open [ 1 ] In Progress [ 3 ]
        Alex Rudyy made changes -
        Alex Rudyy made changes -
        Status In Progress [ 3 ] Ready To Review [ 10006 ]
        Alex Rudyy made changes -
        Assignee Alex Rudyy [ alex.rufous ] Keith Wall [ k-wall ]
        Keith Wall made changes -
        Status Ready To Review [ 10006 ] Resolved [ 5 ]
        Resolution Fixed [ 1 ]
        Keith Wall made changes -
        Description The Java broker currently has a suite of manual persistent store tests. These tests should be automated as part of the System Test suite.

        BDB-Qpid-1 Verifies that committed messages survive clean broker shutdown, after fully completing a number of transactions.
        BDB-Qpid-2 Verifies that committed messages survive immediate (kill -9) broker shutdown, after fully completing a number of transactions.
        BDB-Qpid-5 Verifies that committed messages survive clean broker shutdown, when broker is shutdown mid-transaction.
        BDB-Qpid-6 Verifies that committed messages survive immediate (kill -9) broker shutdown, when broker is shutdown mid-transaction.
        BDB-Qpid-7 Verifies that committed messages survive client connection termination, when clients connection is closed mid-transaction.
        BDB-Qpid-8 Verifies that committed messages survive message store backup and restore, when broker is restarted on a restored backup.

        The non-store implementation specific tests should be incorporated into the PersistentStoreTest system test. The test BDB-Qpid-8 is BDB specific and a should be implemented as in BDB specific system test.

        QBTC will need to be extended to permit the shutting down the Broker down gracefully (using kill -15). Currently the framework uses java.lang.Process#destroy() which is implemented as kill -9.
        The Java broker currently has a suite of manual persistent store tests. These tests should be automated as part of the System Test suite.

        BDB-Qpid-1 Verifies that committed messages survive clean broker shutdown, after fully completing a number of transactions.
        BDB-Qpid-2 Verifies that committed messages survive immediate (kill -9) broker shutdown, after fully completing a number of transactions.
        BDB-Qpid-5 Verifies that committed messages survive clean broker shutdown, when broker is shutdown mid-transaction.
        BDB-Qpid-6 Verifies that committed messages survive immediate (kill -9) broker shutdown, when broker is shutdown mid-transaction.
        BDB-Qpid-7 Verifies that committed messages survive client connection termination, when clients connection is closed mid-transaction.
        BDB-Qpid-8 Verifies that committed messages survive message store backup and restore, when broker is restarted on a restored backup.

        The non-store implementation specific tests should be incorporated into the PersistentStoreTest system test. The test BDB-Qpid-8 is BDB specific and a should be implemented as in BDB specific system test.

        QBTC will need to be extended to permit the shutting down the Broker down ungracefully (using kill -9). Currently the framework uses java.lang.Process#destroy() which is implemented as kill -15.
        Keith Wall made changes -
        Status Resolved [ 5 ] Closed [ 6 ]
        Keith Wall made changes -
        Fix Version/s 0.15 [ 12319043 ]
        Keith Wall made changes -
        Resolution Fixed [ 1 ]
        Status Closed [ 6 ] Reopened [ 4 ]
        Keith Wall made changes -
        Status Reopened [ 4 ] In Progress [ 3 ]
        Keith Wall made changes -
        Status In Progress [ 3 ] Ready To Review [ 10006 ]
        Keith Wall made changes -
        Assignee Keith Wall [ k-wall ] Alex Rudyy [ alex.rufous ]
        Alex Rudyy made changes -
        Status Ready To Review [ 10006 ] Resolved [ 5 ]
        Resolution Fixed [ 1 ]
        Keith Wall made changes -
        Assignee Alex Rudyy [ alex.rufous ] Keith Wall [ k-wall ]
        Keith Wall made changes -
        Assignee Keith Wall [ k-wall ] Robbie Gemmell [ gemmellr ]

          People

          • Assignee:
            Robbie Gemmell
            Reporter:
            Keith Wall
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development