Uploaded image for project: 'camunda BPM'
  1. camunda BPM
  2. CAM-10339

Document Mocks in combination with ProcessEngineRule

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Fixed
    • Icon: L3 - Default L3 - Default
    • 7.11.0
    • None
    • documentation
    • None

      What are the steps to reproduce your problem?
      1. process definition with timer start event
      2. timer definition references a bean, e.g.

      ${timerCycle}

      3. the unit test, using ProcessEngineRule, Mocks.register and @Deployment

      What is the problem?
      When Mocks.register is declared in @Before method, the deployment fails, as before-method is too late to mock the bean for timer start event

      What would be the expected behavior:
      We should document this peculiarity and give a hint in the docs of how this can be overcome.

      Hints (optional):
      Another JUnit rule could be created and the rule chain could be built with ProcessEngineRule

        This is the controller panel for Smart Panels app

            [CAM-10339] Document Mocks in combination with ProcessEngineRule

            Thorben Lindhauer added a comment -

            Resolved via https://github.com/camunda/camunda-docs-manual/pull/231

            Thorben Lindhauer added a comment - Resolved via https://github.com/camunda/camunda-docs-manual/pull/231

              svetlana.dorokhova Svetlana Dorokhova
              svetlana.dorokhova Svetlana Dorokhova
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: