Uploaded image for project: 'Arquillian'
  1. Arquillian
  2. ARQ-803

Mark the skipped tests somehow in JUnit reports when the container failed to boot.

    XMLWordPrintable

Details

    • Enhancement
    • Resolution: Unresolved
    • Major
    • None
    • 1.0.0.CR5
    • Test Harness Integration
    • None

    Description

      Only one test log contains the reason why the server didn't boot.
      It's hard to find it.
      If the .xml file contained a special attribute, it would be much easier.

      Other option is to mark the successive skipped tests as SKIPPED, but that would be kinda misuse of that.

      Attachments

        Issue Links

          is related to

          Bug - A problem that impairs or prevents the functions of the product. WFLY-576 Testsuite tasks (tracking)

          • 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

              Unassigned Unassigned
              ozizka_jira Ondrej Zizka (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

                Created:
                Updated: