Uploaded image for project: 'Camunda Optimize'
  1. Camunda Optimize
  2. OPT-3182

Refactor EventClient

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Won't Do
    • Icon: L3 - Default L3 - Default
    • 3.0.0-alpha2, 3.0.0
    • None
    • backend
    • None

      Context:
      The `org.camunda.optimize.test.optimize.EventClient` is currently deviating from all other client implementation in the scope of integration tests.
      They usually only cover the rest api access but in the EventClient also elasticsearch as well as internal Optimize services are accessed. To reduce complexity of this client and allow easier reuse we should extract the elasticsearch & optimize service parts out of it.

      AT:

      • elasticsearch aspects are either extracted to a dedicated component or added to the ElasticSearchIntegrationTestExtension
      • optimize service access is moved to the EmbeddedOptimizeExtension
      • it's ctor is aligned with the other clients to take a requestExecutor supplier

        This is the controller panel for Smart Panels app

              Unassigned Unassigned
              sebastian.bathke Sebastian Bathke
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved: