Uploaded image for project: 'Subscription Watch'
  1. Subscription Watch
  2. SWATCH-3558

Design testing pattern/strategy for how to test "do nothing" behavior

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Done
    • Icon: Normal Normal
    • None
    • None
    • Automation
    • 5
    • False
    • Hide

      None

      Show
      None
    • True
    • subs-swatch

      While refining SWATCH-2912, it became evident that we need to establish a pattern for testing the following flow:

      • A component consumes a kafka message
      • The component decides it doesn't want to do anything with that message, so there's not output message to use for verification

      It's not enough to consider "there's no output, so it must have worked", because we don't know if the lack of output was intentional or due to an error with the component.

      We started discussing this during a team meeting on 5/7/25. This card is to refer to the notes from that discussion and come up with a test strategy based on that.

      Acceptance Criteria:

      • Draft up a proposal of a test strategy for these types of tests.
      • Review with the team in a future meeting.

      After the test strategy is agreed upon, it can then be implemented in IQE as part of SWATCH-2912.

              jcarvaja@redhat.com Jose Carvajal Hilario
              lburnett0 Lindsey Burnett
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: