Add coverage to all variants

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Unknown
    • None
    • Affects Version/s: None
    • Component/s: Infrastructure
    • None
    • 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?
    • None
    • None
    • None
    • None
    • None
    • None

      Context

      We don't have coverage reports across all of our test suites. By doing this, then we will a better perspective of what parts of our codebase aren't done. Right now only the mainline test suites have coverage running. This change means that for every test suite, we will need to run an additional "coverage" task.

      Acceptance Criteria

      Run an additional coverage task for every test suite that doesn't already have coverage

      Pitfalls

      This will balloon our evergreen tests. We may not need to run it periodically, but we should run it on every PR. This should not include some Github Actions. 

      Make sure there is a team agreed upon decision on what is run during PR and what – if anything – is run periodically for coverage tests.

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

              Created:
              Updated: