Uploaded image for project: 'Couchbase .NET client library'
  1. Couchbase .NET client library
  2. NCBC-1378

Add couchbasemock testing support in support of kverror map

    XMLWordPrintable

Details

    • New Feature
    • Status: Resolved
    • Blocker
    • Resolution: Done
    • None
    • 2.4.7
    • None
    • None

    Description

      Goal is to be able to run under unit tests, but disabled by default, a set of tests that use couchbasemock. The initial test here should be retrieving the kverror map successfully. In future, will add additional tests for kverrormap retries.

      Attachments

        Issue Links

          No reviews matched the request. Check your Options in the drop-down menu of this sections header.

          Activity

            I raised this question on HipChat earlier today:

            "

            [11:58 AM] Mike Goldsmith: I've just had a brain-wave while preparing my RBAC Show & Tell material and come up with a problem I can't get around:

            • What if you want a password-less bucket?

            Pre-spock you would just not give the bucket a password, with Spock you're not allowed a password-less user. This leads to questions like:

            • What happens if an existing cluster is upgraded to 5.0 where there are password-less buckets?

            I believe the upgrade is meant to create users for each bucket, with the same password, to provide backward compatibility. What if there isn't a password? I would agree most production systems will use bucket passwords, but what about existing dev environments?

            [12:11 PM] Mike Goldsmith: This also has a further complication of client testing where I'm certain a significant portion of each client's integration tests will target the 'default' bucket where you are unable to set a password.
            "
            If want to move all integration tests to CouchbaseMock, we'll have to be aware that the majority of our tests currently target a password-less bucket. I think that is correct way to go, but wanted to highlight there could more effort than simply switching the target.

            mike.goldsmith Michael Goldsmith added a comment - I raised this question on HipChat earlier today: " [11:58 AM] Mike Goldsmith: I've just had a brain-wave while preparing my RBAC Show & Tell material and come up with a problem I can't get around: What if you want a password-less bucket? Pre-spock you would just not give the bucket a password, with Spock you're not allowed a password-less user. This leads to questions like: What happens if an existing cluster is upgraded to 5.0 where there are password-less buckets? I believe the upgrade is meant to create users for each bucket, with the same password, to provide backward compatibility. What if there isn't a password? I would agree most production systems will use bucket passwords, but what about existing dev environments? [12:11 PM] Mike Goldsmith: This also has a further complication of client testing where I'm certain a significant portion of each client's integration tests will target the 'default' bucket where you are unable to set a password. " If want to move all integration tests to CouchbaseMock, we'll have to be aware that the majority of our tests currently target a password-less bucket. I think that is correct way to go, but wanted to highlight there could more effort than simply switching the target.
            jmorris Jeff Morris added a comment -

            Will be merged for 2.4.7

            jmorris Jeff Morris added a comment - Will be merged for 2.4.7

            People

              mike.goldsmith Michael Goldsmith
              ingenthr Matt Ingenthron
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Gerrit Reviews

                  There are no open Gerrit changes

                  PagerDuty