Authentication test variants should use their own set of tasks

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Done
    • Priority: Unknown
    • None
    • Affects Version/s: None
    • Component/s: Infrastructure
    • None
    • Python Drivers
    • Not Needed
    • None
    • None
    • None
    • None
    • None
    • None

      Context

      Currently, we use our test-non-standard EG task for auth test variants. This task cycles through the python version, server version, and topology when creating test tasks, but since we only use auth on sharded, the specifics of the cycle can result in gaps in coverage. Most notably, free-threaded Python can fail to be paired with a sharded topology, preventing auth + free-threaded from being tested.

      Definition of done

      Use a new test-standard-auth EG task for auth test variants. Look to create_test_non_standard_tasks as a template for creating a new create_test_standard_auth_tasks function. This function should look very similar but should only use sharded topologies and should name its generated tasks test-standard-auth. All auth variant generation methods should have their tasks updated from .test-non-standard to .test-standard-auth to use these new tasks.

      Pitfalls

      N/A.

            Assignee:
            Casey Clements
            Reporter:
            Noah Stapp
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: