Uploaded image for project: 'Node.js Driver'
  1. Node.js Driver
  2. NODE-6615 Add integration tests that assert client.close() cleans up all resources
  3. NODE-6620

Add integration Node.js resource test structure and file read tests for improved client.close()

XMLWordPrintableJSON

    • Type: Icon: Sub-task Sub-task
    • Resolution: Fixed
    • Priority: Icon: Unknown Unknown
    • 6.13.0
    • Affects Version/s: None
    • Component/s: None
    • 0
    • Not Needed
    • 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... node.js driver engineer
      I want... to ensure that client.close() cleans up all relevant node.js resources within a process
      So that... I know the driver accurately performs clean-up

      Acceptance Criteria

      Implementation Requirements

      • For each relevant node.js resource
        • Run a child process
        • Create the resource
        • Assert the resource has been created through sinon or libuv report
        • Close the client
        • Assert no new resources remain through the following:
          • libuv report
          • beforeExit JS event
        • Close the process
      • See table in the design doc for further explanation on 'relevant server and node resources'

      Follow Up Requirements

      • Align integration tests with new tests cases that arise as the design finalizes

            Assignee:
            aditi.khare@mongodb.com Aditi Khare
            Reporter:
            aditi.khare@mongodb.com Aditi Khare
            Bailey Pearson
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: