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

WildFlyRunner doesn't call tearDown and completed ServerSetupTasks if a later one fails in setup

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Minor Minor
    • None
    • None
    • Test Suite
    • None

      If a test class declares multiple ServerSetupTask classes in @ServerSetup and a task after the first one fails, tearDown is never called for the tasks that successfully executed setup.

      I've used Minor priority for this only because we haven't gotten complaints. Conceptually it's pretty significantly wrong behavior.

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

              Created:
              Updated: