Test that updating the engine-alias in the configuration does not affect functionality

XMLWordPrintable

      Context:
      We once encountered the case that a customer updated the engine-alias in the environment config which causes a NullPointerException when definitions for this no longer existing engineAlias were retrieved from the definition index.

      AT:

      • test that updating the engineAlias and restarting Optimize should have no negative impact on
        • retrieving definitions
        • evaluation of reports

        This is the controller panel for Smart Panels app

              Assignee:
              Unassigned
              Reporter:
              Sebastian Bathke
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved: