Uploaded image for project: 'RESTEasy'
  1. RESTEasy
  2. RESTEASY-1884

Consider to get rid of additional surefire executions in resteasy testsuite

    XMLWordPrintable

Details

    • Task
    • Resolution: Done
    • Major
    • 4.0.0.Beta7, 3.6.3.Final
    • 4.0.0.Beta3, 3.6.0.Final
    • None
    • None

    Description

      Based on discussion on PR1498, we may consider to get rid of additional executions in testsuite.

      Currently, there are two additional executions:

      GZIP execution

      • Main reason of this execution is using additional system property in server (passed to arquillian)
      • Currently, arquillian uses only one container. This container is started only once in integration-tests module before execution of all its tests. This container is stopped after all tests are executed.
      • Arquillian could use more containers, each container could have different settings/configuration. See this example from manual mode of AS TS, this file contains definition of 16 containers. Container runs in mode manual, it means, that test needs to start server by javacode, like this example. If we want to apply this approach to whole integration-tests module, all tests should have some logic for starting/stopping of containers. It leads to rewriting of all tests in integration-tests module ...
      • We can create new module (with arquillian mode manual) and store this kind of tests to that new module. Currently, this new module will have only this 4 test cases. This is probably the best approach for getting rid of gzip surefire execution
      • Arquillian could use more containers and starts all containers before test executions. This approach is used in multinode module from as ts. Containers are not started in mode=manual. At least, all non-RunAsClient tests from integration-modules needs to be updated, see this. Two EAP running in parallel could also cause more env-issues, because that consumes more memory resources.

      JSON-B execution

      • Main reason for this profile is excluding of json-b dependency, see github code
      • This is client-side settings, so AFAIK, we can't get rid of this execution by some arquillian settings
      • We can get rid of this surefire execution by creating of new module only for this 1 test case

      Feel free to update description of this jira && find out better approach.

      Arquillian modes are described here

      cc: asoldano

      Attachments

        Activity

          People

            jbliznak@redhat.com Jan Blizňák
            mkopecky@redhat.com Marek Kopecky
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: