Identify all parts of the code that are unused/untested

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Minor - P4
    • None
    • Affects Version/s: None
    • Component/s: Infrastructure, Internal, Tests
    • None
    • 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?
    • None
    • None
    • None
    • None
    • None
    • None

      Context

      Once PYTHON-3898 is completed and coverage tests are added to all variants, we expect some files to have low coverage. We need to identify what these modules. So we should look through each module's coverage and determine if uncovered sections are unused or simply untested.

      Acceptance Criteria

      Once a coverage report is done, new tickets created for files with low coverage (<%70 criteria flexible but agreed upon by the team) to be deleted or have new tests added.

      Pitfalls 

      100% code coverage is desired but may not always be achievable and could severely bloat the number of tests. Discussing a coverage threshold is a good way to avoid scope creep.

            Assignee:
            Unassigned
            Reporter:
            Shane Harvey
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: