Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-56168

Understand and Reduce gap in test coverage w.r.t. feature flagging

    XMLWordPrintable

Details

    • Fully Compatible
    • STM 2021-07-26, STM 2021-08-09, STM 2021-08-23, STM 2021-09-06, STM 2021-09-20, STM 2021-10-04, STM 2021-10-18, STM 2021-11-15, STM 2022-01-10, STM 2022-01-24, Dev Platform 2022-05-30, Dev Platform 2022-06-13, Dev Platform 2022-06-27, Dev Platform 2022-07-11, Dev Platform 2022-07-25
    • 2

    Description

      During the MongoDB 5.0 release cycle, code under active development has been tested less often (in terms of compute hours) than the code which isn't. Notably, the InMemory and the large transactions format variants do not have 'all feature flags' equivalents.

      I really want to emphasize that continuous integration means switching the feature from off-by-default to on-by-default is a non-event because the feature has been slowly expanding its testing coverage over time until the flip.

      Attachments

        Issue Links

          Activity

            People

              robert.guo@mongodb.com Robert Guo
              robert.guo@mongodb.com Robert Guo
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated: