Update InitialSyncTest unit test to avoid hardcoding FCV constants

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 5.1.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • Repl 2021-07-12, Repl 2021-07-26
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      In InitialSyncerReturnsParseErrorWhenFCVFetcherReturnsNoVersion, we hardcode an FCV 4.4 constant. As a result, after upgrading to 5.0 LTS, this will break. We should update the unit test to use a GenericFCV constant or find some alternative way of testing the behavior.

            Assignee:
            Vesselina Ratcheva (Inactive)
            Reporter:
            Xuerui Fa
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: