ExportXMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Server Programmability
    • Programmability 2026-08-04
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Currently, the C++ integration test tasks are organized according to the fixture they spawn or what feature flags and server paramters they use. For an example of simple fixture-based organization, integration_tests_replset is most C++ integration tests that run against a replica set. For an example of feature flagging, integration_tests_standalone_grpc runs a small set of C++ integration tests against a server with ingress gRPC enabled.

      To support infinite burndown, this change splits those tasks into functionality-based tasks that can be owned by individual teams. For example, integration_tests_bson_replset runs BSON-related integration tests against a replset. This does yield a quadratic number of tasks i.e., most of the matrix coming from combining

      {functional groups}

      X

      {fixture groups}

      needs its own task. In addition, if adding a new integration test binary, one now has to ensure that it gets added to a test suite rather than being orphaned since suites previously picked up "everything except what this suite denies" and they now pick up "exactly what this suite wants to test and no more."

            Assignee:
            Ryan Berryhill
            Reporter:
            Ryan Berryhill
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: