Implement the changestream verification logic for each possible scenario

XMLWordPrintableJSON

    • Type: Sub-task
    • Resolution: Won't Do
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Query Execution
    • QE 2025-09-29, QE 2025-10-13, QE 2025-10-27, QE 2025-12-08, QE 2025-11-24, QE 2025-11-10
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      For each possible scenario, we generate. We need to provide a class for verifying that the events received on the changestream are actually matching with the expectations. 

      The difficulty here is to track the list of actions and provide a customizable event checker to attach to the end state for each possible scenario. 

       

      E.G

       

      DabatabasePresentCollectionPresent<StartState> => insert doc => DabatabasePresentCollectionPresent<Event Checker> 

      EventChecker will need to verify that changestream has received insert on the collection and possibly that the collection was setup correctly at the beginning.  

            Assignee:
            Nicola Cabiddu
            Reporter:
            Nicola Cabiddu
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: