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

Audit skipped tests in driver main

    • 2
    • Not Needed
    • Hide

      Create a copy of the Kickoff Template with the issue key (NODE-XXX) in the filename and share a link to the new doc via this field.

      Show
      Create a copy of the Kickoff Template with the issue key (NODE-XXX) in the filename and share a link to the new doc via this field.
    • 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 driver engineer
      I want... to make sure we are prioritizing unskipping high value tests
      So that... we maintain proper test coverage and are able to catch regressions

      User Impact

      • Fewer bugs making it through

      Dependencies

      • N/A

      Unknowns

      • N/A

      Acceptance Criteria

      Implementation Requirements

      • Identify all test skips marked with TODO NODE-xxxx
      • Add a "skipped-test" label to the corresponding ticket
      • Mark the ticket with the correct priority based on the following criteria:
        • P2 - Skipping this test is creating a significant gap in our coverage / puts us at significant risk of regressions (the functionality is not an edge case and there is no running test that's likely to catch a regression in this case)
        • P3 - Skipping this test is undesirable but isn't likely to cause significant problems (there exist other tests that would likely catch a regression in this area OR it would be hard to break this functionality without breaking many other things that we do test OR the functionality is an edge case that rarely occurs "in the wild")
        • P4 - This test covers an extremely unlikely edge case OR this test is of questionable value but would need further investigation to decide whether it should be reworked or removed entirely

      Testing Requirements

      • N/A

      Documentation Requirements

      • N/A

      Follow Up Requirements

      • N/A

            Assignee:
            bailey.pearson@mongodb.com Bailey Pearson
            Reporter:
            daria.pardue@mongodb.com Daria Pardue
            Neal Beeken
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: