• Type: Icon: New Feature New Feature
    • Resolution: Won't Do
    • Priority: Icon: Minor - P4 Minor - P4
    • None
    • Affects Version/s: None
    • Component/s: Testing
    • Hide

      1. What would you like to communicate to the user about this feature?
      2. Would you like the user to see examples of the syntax and/or executable code and its output?
      3. Which versions of the driver/connector does this apply to?

      Show
      1. What would you like to communicate to the user about this feature? 2. Would you like the user to see examples of the syntax and/or executable code and its output? 3. Which versions of the driver/connector does this apply to?

      At the moment we test only against the latest server, deployed as a standalone. As we expand the MongoDB configurations we test against, the C++ Driver will have to check how MongoDB is configured and decide which tests to skip and what expectations to assert within tests, the same as other drivers.

      Let's follow PyMongo's lead: once when the tests start, call "isMaster" and fill out a struct of information about the deployment, such as its min and max wire versions, whether it is a replica set, the number of nodes, whether test commands are enabled, etc.

      "Catch" allows test fixtures with a relevant example:

      https://github.com/catchorg/Catch2/blob/master/docs/test-fixtures.md#top

            Assignee:
            Unassigned Unassigned
            Reporter:
            jesse@mongodb.com A. Jesse Jiryu Davis
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: