Uploaded image for project: 'Red Hat Advanced Cluster Management'
  1. Red Hat Advanced Cluster Management
  2. ACM-16832

Make maestro integration cases can be run independently against MQTT and gRPC broker

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Major Major
    • None
    • None
    • Maestro
    • False
    • Hide

      None

      Show
      None
    • False
    • None

      Value Statement

      Currently, the integration tests rely on MQTT as the broker, with some test cases dependent on MQTT. We need to refactor the tests to ensure they are independent and can be run against either MQTT or gRPC brokers.

      Definition of Done for Engineering Story Owner (Checklist)

      • ensure integration test can be run against MQTT or gRPC broker
      • ensure no dependency on broker type for test cases.

      Development Complete

      • The code is complete.
      • Functionality is working.
      • Any required downstream Docker file changes are made.

      Tests Automated

      • [ ] Unit/function tests have been automated and incorporated into the
        build.
      • [ ] 100% automated unit/function test coverage for new or changed APIs.

      Secure Design

      • [ ] Security has been assessed and incorporated into your threat model.

      Multidisciplinary Teams Readiness

      • [ ] Create an informative documentation issue using the Customer

      Portal Doc template that you can access from [The Playbook](

      https://docs.google.com/document/d/1YTqpZRH54Bnn4WJ2nZmjaCoiRtqmrc2w6DdQxe_yLZ8/edit#heading=h.9fvyr2rdriby),

      and ensure doc acceptance criteria is met.

      • Call out this sentence as it's own action:
      • [ ] Link the development issue to the doc issue.

      Support Readiness

      • [ ] The must-gather script has been updated.

              lcao@redhat.com Longlong Cao
              lcao@redhat.com Longlong Cao
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: