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

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

      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.

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

              Created:
              Updated: