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

Monkey test the Optimize UI

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Unresolved
    • Icon: L3 - Default L3 - Default
    • None
    • None
    • continuous integration, frontend
    • None
    • Not defined

      AT:

      • it is possible to run monkey testing in the front-end
      • if an error occurred during the monkey test, it is easy possible to see what the error of the test was
      • there is a nightly jenkins job that performs the monkey testing

      Context:
      While developing a web application, did you anticipate uncommon user interactions? Did you manage to detect and patch all memory leaks? If not, the application may break sooner or later. If n random actions can make an application fail, it's better to acknowledge it during testing, rather than letting users discover it.

      Hints:
      One possible option: https://github.com/marmelab/gremlins.js

        This is the controller panel for Smart Panels app

            [OPT-2231] Monkey test the Optimize UI

            Omran Abazeed added a comment -

            This ticket was migrated to github: https://github.com/camunda/camunda-optimize/issues/10555. Please use this link for any future references and continue any discussion there.

            Omran Abazeed added a comment - This ticket was migrated to github: https://github.com/camunda/camunda-optimize/issues/10555 . Please use this link for any future references and continue any discussion there.

              Unassigned Unassigned
              johannes.heinemann Johannes
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: