ExportXMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Replication
    • Repl 2026-10-26
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Currently whenever a new oplog entry type is introduced, the engineers who introduced the new oplog entry type need to remember to test the new oplog type with magic restore.

      We should add a test that:

      1. Runs an engineer written workload
      2. Takes the list of all oplog types from the IDL file
      3. Asserts that the oplog entry type was generated by the workload written by the engineer

      When new oplog entry types are added, the test will fail and so engineers will remember to add testing for their oplog entry type to the workload.

      Ideally the test would look at all the oplog entry types from the IDL file and figure out how to test them. But that's hard because it's not obvious what commands to run on the server to generate a particular oplog entry type.

      We have an ASC magic restore passthrough that should hopefully generate all the various types of oplog entries that can be encountered, so maybe we don't need to do this. Doing this would definitely be more thorough

            Assignee:
            Xuerui Fa
            Reporter:
            Vishnu Kaushik
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: