Audit and move incorrectly placed change streams tests into the sharding folder

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Query Execution
    • QE 2026-06-22, QE 2026-07-06
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Currently change stream jstests are defined in various folders such asĀ 

      • jstests/change_streams/
      • jstests/sharding/query/change_streams/

      The first one expects to be run in passthrough test suites (e.g. "change_streams" suite), while the second runs in a no-passthrough test suite like "sharding", where the test author is responsible for setting the infrastructure and test fixtures.

      Unfortunately, some tests are currently defined in the jstests/change_streams/ folder that set up their own infrastructure and test fixture (the ShardingTest test fixture). An example of this is jstests/change_streams/oplog_rewrite/change_stream_basic_match_pushdown_rewrite.js.

      The goal of this ticket is to inspect the tests in folder jstests/change_streams/, and move them to the jstests/sharding/query/change_streams/ folder if they set up their own ShardingTest test fixure.
      Files can easily be moved around, but the moved files may still be referenced in selector patterns, test inclusions or exclusions of various change streams-related test suite definitions inside buildscripts/resmokeconfig/suites/, buildscripts/resmokeconfig/matrix_suites/, buildscripts/modules/atlas/suites/, and buildscripts/modules/atlas/matrix_suites/.
      The test suite definitions need to be adjusted as well so that they account for any moved files.

            Assignee:
            Unassigned
            Reporter:
            Denis Grebennicov
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: