Uploaded image for project: 'Node.js Driver'
  1. Node.js Driver
  2. NODE-3612

Sync BSON Corpus tests to BSON-EXT

    • Type: Icon: Task Task
    • Resolution: Won't Fix
    • Priority: Icon: Unknown Unknown
    • None
    • Affects Version/s: None
    • Component/s: EJSON, Testing
    • Not Needed
    • 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?

      Use Case

      As a driver engineer
      I want to have bson-ext test with the latest corpus tests.
      So that I have a baseline of correct functionality

      User Impact

      *What is the number of impacted customers? How severe is the impact? Is anyone blocked or broken?

      • It relates to the support of this library either we assert correctness or we don't support bson-ext.

        Dependencies

      • Driver v4

      Unknowns

      • How many spec updates have not made it to BSON-EXT?

      Acceptance Criteria

      • Sync the tests and if they fail and it's not a security issue, file a separate bug unless it's a very quick fix.

      Implementation Requirements

      • Sync tests
      • Fix failures

      Documentation Requirements

      • n/a

      Follow Up Requirements

      • Since this lib is seldom visited is there a way we can get more warning about it falling behind on a spec sync?

            Assignee:
            Unassigned Unassigned
            Reporter:
            neal.beeken@mongodb.com Neal Beeken
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: