Make ServiceContextMongoDTest support instantiation of different storage engines

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Won't Fix
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Testing Infrastructure
    • None
    • Sharding 2017-10-02
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Currently the ServiceContextMongoDTest is the only fixture which instantiates storage engine and many tests depend on that. However it can only create an ephemeralForTest storage engine, which makes it unsuitable for unit-tests, which need to exercise concurrency.

      It should be extended with a constructor, which accepts StorageGlobalParams in order to allow it to be configured with a storage engine:

      ServiceContextMongoDTest(const StorageGlobalParams& storageParams);
      

            Assignee:
            Kaloian Manassiev
            Reporter:
            Kaloian Manassiev
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: