Uploaded image for project: 'Couchbase Python Client Library'
  1. Couchbase Python Client Library
  2. PYCBC-691

Set up Combination Testing for SDK 3 - Server 5.5, 6.0, 6.5

    XMLWordPrintable

Details

    • Task
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • 3.0.0-rc
    • None
    • None
    • 1
    • SDK44: βref(1),CombT,Migration, SDK48: βref(2),CombT,Migr., SDK50: βref(2),CombT,Migr., SDK52: B/GA, Doc:Migr/Stngs/Co, SDK5: Docs, Pathfind Antorized

    Description

      Across 5.5, 6.0 and 6.5 server platforms, set up combination testing to execute regular feature tests across all of these platforms per our build and test plan.

      Note that the plan is to support 6.0 and 6.5 for certain, extending back to 5.5 if tests look good and no significant issues are encountered (despite 5.5 being EOL, but not EOSL in April 2020).

      Since it should be simple to do, add 5.0 just to characterize for known issues to document if possible. No support of 5.0 is planned.

      Attachments

        For Gerrit Dashboard: PYCBC-691
        # Subject Branch Project Status CR V

        Activity

          david.kelly David Kelly added a comment - - edited

          Given that the v2 tests fail due to interface changes, etc... It seems like the first thing to do is get the combination tests running on the v3 tests only. Then, fix the bugs in those (there are several). Then as we convert v2 to v3, our combination tests get better.

          Ideally, we do this:

          • Get it running in Jenkins, restricting to v3 tests only. (with failures)
          • Make it green.
          • Then this ticket is done.
          • Then we convert v2->v3. (which should be a ticket, I'll check)
          david.kelly David Kelly added a comment - - edited Given that the v2 tests fail due to interface changes, etc... It seems like the first thing to do is get the combination tests running on the v3 tests only. Then, fix the bugs in those (there are several). Then as we convert v2 to v3, our combination tests get better. Ideally, we do this: Get it running in Jenkins, restricting to v3 tests only. (with failures) Make it green. Then this ticket is done. Then we convert v2->v3. (which should be a ticket, I'll check)
          david.kelly David Kelly added a comment -

          currently I have a pipeline that executes against a given server and python version. Next I'll nest that in some loops over various pythons and servers. Maybe worth doing 6.5 with and without developer preview on as well.

          david.kelly David Kelly added a comment - currently I have a pipeline that executes against a given server and python version. Next I'll nest that in some loops over various pythons and servers. Maybe worth doing 6.5 with and without developer preview on as well.
          david.kelly David Kelly added a comment -

          The initial pipeline is here: http://sdk.jenkins.couchbase.com/job/python/job/python-integration-pipeline/

          Also some initial work to make the V3 tests was committed. We have a ways to go, but this seems complete enough to call it done.

          david.kelly David Kelly added a comment - The initial pipeline is here: http://sdk.jenkins.couchbase.com/job/python/job/python-integration-pipeline/ Also some initial work to make the V3 tests was committed. We have a ways to go, but this seems complete enough to call it done.

          People

            david.kelly David Kelly
            ingenthr Matt Ingenthron
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Gerrit Reviews

                There are no open Gerrit changes

                PagerDuty