Coverage gap between multiversion burn in and dedicate multiversion suite

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Won't Fix
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Testing Infrastructure
    • None
    • ALL
    • STM 2021-11-15
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      We should add a sanity check for implicit multiversion suites so new behavior that causes breakages in unmodified multiversion tests.

      Problem Example:

      • if someone changes behavior (i.e. protocol for initialization order) on master and modified a test and that suite doesn't run in any multiversion suites, then they won't get any multiversion test coverage.

            Assignee:
            Robert Guo (Inactive)
            Reporter:
            Robert Guo (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: