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

Run integration test suite against Camunda Run

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Won't Fix
    • Icon: L3 - Default L3 - Default
    • None
    • None
    • run
    • None

      Similar to the Camunda Spring Boot Starter and the other Camunda BPM Distros (WildFly, Tomcat, etc.), all integration tests for the REST API and the Webapps should run against the Camunda BPM Run ZIP.

      With CAM-11291, we introduced basic ITs for REST and Webapps that basically run like Arquillian Tests (Test class defines the Managed Container and runs the specified test cases against that managed instance). This newly established Managed Container for Camunda Run could be used in order to

      1. start the container before the integration test suite runs, 
      2. run the integration tests
      3. stop the container after the tests

      We should also consider the different startup and configurations options for the ZIP in those scenarios like

      • REST enabled only
      • Webapps enabled only
      • HTTPS enabled for the distro

        This is the controller panel for Smart Panels app

            [CAM-11379] Run integration test suite against Camunda Run

            Tobias Metzke-Bernstein created issue -
            Tobias Metzke-Bernstein made changes -
            Fix Version/s Original: 7.13.0 [ 15532 ]
            Tobias Metzke-Bernstein made changes -
            Description Original: Tests that should be executed:
            * test the ZIP (unpack it, start the scripts)
            * also consider "common" Spring Boot tests for the new features (Security, etc.)             		New: Similar to the Camunda Spring Boot Starter and the other Camunda BPM Distros (WildFly, Tomcat, etc.), all integration tests for the REST API and the Webapps should run against the REST Distro ZIP.

            With CAM-11291, we introduced basic ITs for REST and Webapps that basically run like Arquillian Tests (Test class defines the Managed Container and runs the specified test cases against that managed instance). This newly established Managed Container for our REST Distro could be used in order to
            # start the container before the integration test suite runs, 
            # run the integration tests
            # stop the container after the tests
            Tobias Metzke-Bernstein made changes -
            Mentioned Roles
            Tobias Metzke-Bernstein made changes -
            Mentioned Groups
            Tobias Metzke-Bernstein made changes -
            Mentioned Roles
            Tobias Metzke-Bernstein made changes -
            Mentioned Groups
            Tobias Metzke-Bernstein made changes -
            Status Original: Open [ 1 ] New: Ready [ 10005 ]
            Tobias Metzke-Bernstein made changes -
            Assignee Original: Tobias Metzke-Bernstein [ tobias.metzke ]
            Tobias Metzke-Bernstein made changes -
            Link New: This issue is related to CAM-11291 [ CAM-11291 ]
            Tobias Metzke-Bernstein made changes -
            Description Original: Similar to the Camunda Spring Boot Starter and the other Camunda BPM Distros (WildFly, Tomcat, etc.), all integration tests for the REST API and the Webapps should run against the REST Distro ZIP.

            With CAM-11291, we introduced basic ITs for REST and Webapps that basically run like Arquillian Tests (Test class defines the Managed Container and runs the specified test cases against that managed instance). This newly established Managed Container for our REST Distro could be used in order to
            # start the container before the integration test suite runs, 
            # run the integration tests
            # stop the container after the tests             		New: Similar to the Camunda Spring Boot Starter and the other Camunda BPM Distros (WildFly, Tomcat, etc.), all integration tests for the REST API and the Webapps should run against the REST Distro ZIP.

            With CAM-11291, we introduced basic ITs for REST and Webapps that basically run like Arquillian Tests (Test class defines the Managed Container and runs the specified test cases against that managed instance). This newly established Managed Container for our REST Distro could be used in order to
            # start the container before the integration test suite runs, 
            # run the integration tests
            # stop the container after the tests

            We should also consider the different startup and configurations options for the ZIP in those scenarios like
            * REST enabled only
            * Webapps enabled only
            * HTTPS enabled for the distro
            Tobias Metzke-Bernstein made changes -
            Mentioned Roles
            Tobias Metzke-Bernstein made changes -
            Mentioned Groups

              Unassigned Unassigned
              tobias.metzke Tobias Metzke-Bernstein
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: