Uploaded image for project: 'WildFly Core'
  1. WildFly Core
  2. WFCORE-6740

[Community] Add a base ServerSetupTask class for checking assumptions

XMLWordPrintable

    • Icon: Feature Request Feature Request
    • Resolution: Unresolved
    • Icon: Minor Minor
    • None
    • None
    • Test Suite
    • None

      Requires WFARQ-160.

      Add a testsuite/shared util class that can be the base for ServerSetupTask impls that just check assumptions and throw AssumptionViolatedException.

      The class should accept an optional BiFunction<ManagementClient, String> as a constructor param and then a protected void checkAssumptions(ManagementClient, String) method that does nothing. The setup and tearDown methods call the BiFunction if it exists and then call checkAssumptions.

      The two mechanisms are meant to satisfy different programming patterns. A ServerSetupTask is instantiated by the test runner using a no-arg constructor, so subclassing and overriding checkAssumptions is a natural programming model. OTOH for use cases like WFLY-19126 providing a function may be a better fit.

      Or some better way. The basic point is to make it easy to write a task that just does assumption checks, to be used early on in a series of tasks, allowing the later tasks to just focus on doing, not checking.

            Unassigned Unassigned
            bstansbe@redhat.com Brian Stansberry
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: