Decide the destiny of the async step-down tests and formalize the coverage proof

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Storage Engines - Foundations
    • 220.137
    • None
    • None

      Follow-up to WT-18220. The async step-down testing now spans the suites from WT-17897 and WT-18155 plus the gap-closing validation branch from WT-18220.

      The task: carefully review all the tests added around stepping down and decide for each which form it should take — remain a deterministic Python test, be covered by stress testing only (test/format WT-18044, the agreed test_layered_cursor_stress.py extension), or be dropped as too minor to spend time on. The outcome should include some form of formal proof of what is covered and what is not. The coverage matrix attached to WT-18220 can serve as a starting point; one option is making it executable — scenario tests and the document generated from a single data file, with a checker that every matrix cell maps to an existing test — but the form is the assignee's choice.

            Assignee:
            [DO NOT USE] Backlog - Storage Engines Team
            Reporter:
            Ivan Kochin
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: