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

ProcessEngineRule does not work in parameterized JUnit tests

XMLWordPrintable

    • Icon: Bug Report Bug Report
    • Resolution: Fixed
    • Icon: L3 - Default L3 - Default
    • 7.3.0, 7.2.5, 7.3.0-alpha3
    • None
    • engine
    • None

      Problem description
      When ProcessEngineRule is used in a parameterized JUnit test, the name of the bpmn file to be deployed is not detected correctly.

      Context:
      1) It is possible to annotate a testmethod with @Deployment. If the annotation is used without a parameter, the filename of the bpmn file to be deployed is determined based on the name of the Package, Class and Method. The name of the method is determined using org.junit.runner.Description.getMethodName()
      => In case of a parameterized JUnit test, getMethodName() returns the name of the method postfixed with the id of the run eg testSomething[1] ...

      2) Note that this is a regression (worked in Camunda <= 7.1) which was introduced with the upgrade of JUnit and the fact that ProcessEngineRule now extends TestWatcher instead of the deprecated TestWatchman class.

      Expected behavior:
      Parameterized JUnittests work

        This is the controller panel for Smart Panels app

              smirnov Roman Smirnov
              meyer Daniel Meyer
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: