Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-576 Testsuite tasks (tracking)
  3. WFLY-616

TS: Clustering tests - figure out how they will be run

    XMLWordPrintable

Details

    • Sub-task
    • Resolution: Done
    • Major
    • 8.0.0.Final
    • None
    • None
    • None

    Description

      The current single test is not multinode - when set up as multinode, it fails. So it runs as single node, even though being in package .cluster.

      Attachments

        Issue Links

          blocks

          Feature Request - Feature requests from customers and/or users AS7-3954 TS clustering: test with different JGroups stack

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Feature Request - Feature requests from customers and/or users AS7-4051 TS: Clustering tests are relying on the fact that node0 and node1 are the same domain for cookies

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          incorporates

          Bug - A problem that impairs or prevents the functions of the product. AS7-2847 TS: Clustering tests cannot be run for single test with -Dtest=X

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved
          is blocked by

          Feature Request - Feature requests from customers and/or users ARQ-674 @OperateOnDeployment to allow test to operate on 2 deployments

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed

          Feature Request - Feature requests from customers and/or users ARQ-336 Inject container references in the test to start/stop containers

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Feature Request - Feature requests from customers and/or users ARQ-648 Implement @ArquillianResource Map<URL> for multi-container configuration.

          • Critical - To be worked on immediately following BLOCKER issues.
          • Open

          Bug - A problem that impairs or prevents the functions of the product. AS7-2837 Current AS7 clustering tests do not test <distributable/> webapp

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. AS7-2779 Regression in AS7-1242 -- arquillian-service is only deployed to first container in group

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          relates to

          Bug - A problem that impairs or prevents the functions of the product. AS7-3808 CacheLoaderException: Root not directory or IO error occurred

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              rhn-engineering-rhusar Radoslav Husar
              ozizka_jira Ondrej Zizka (Inactive)
              Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: