Add tests closing the identified async step-down coverage gaps on a validation branch

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Done
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Test Python
    • None
    • Storage Engines - Foundations, Storage Engines - Transactions
    • 0.051
    • SE Transactions - 2026-07-31
    • 3

      We did an analysis of the async step-down test coverage added in WT-17897 and WT-18155, reviewed against the implementation from WT-17895. The analysis identified a number of potential coverage gaps — cases missing from the existing test classes, cross-class interactions, and a few whole classes with no coverage (e.g. reads resolving through the history store, maintenance operations while the step-down timestamp is set, cursor-handle reuse across step-down events). A document with the full gap list and a coverage matrix will be attached to this ticket.

      The task: generate tests (AI-assisted) closing the identified gaps, put them on a branch and run them against the async step-down logic. The goal of the branch is to find bugs and validate the gap list — it should NOT be merged as-is. Deciding what from the branch is worth keeping is a separate task (see the follow-up ticket).

            Assignee:
            Zunyi Liu
            Reporter:
            Ivan Kochin
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: