Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-21581

Clustering Testsuite V3 (epic)

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • 39.0.0.Final, 39.0.1.Final
    • Clustering, Test Suite
    • None
    • ---
    • ---

      This is an epic tracker for changes we need to implement in WildFly Clustering test suite so that it can be efficiently used.

      The core issues are that legacy JUnit 4 framework is incompatible with components to reuse from upstream, inability to run single test or group of tests without convoluted exclusions and not not leveraging containers for integration tests, and redundant/duplicated tests.

      The order of items to do:

      1. Upgrade to JUnit 5 Jupiter (completed)
      2. Label test categories and use it to drive executed tests for cases like provisioning and test splitting (not yet started)
      3. Remove all surefire executions and keep a single execution (design started)
      4. Replace infinispan with testcontainers (dev started)
      5. Integrate database containers for integration testing (dev completed, not yet submitted)
      6. Prune tests that are no longer required and are redundant (not yet started)
      7. Replace core tests with abstractions from wildfly-clustering (not yet started)

              rhn-engineering-rhusar Radoslav Husar
              rhn-engineering-rhusar Radoslav Husar
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: