JBehave
  1. JBehave
  2. JBEHAVE-401

XML Scenario reporter doesn't always include a closing story xml tag

    Details

    • Type: Bug Bug
    • Status: Resolved Resolved
    • Priority: Major Major
    • Resolution: Duplicate
    • Affects Version/s: 3.1.2
    • Fix Version/s: 3.2
    • Component/s: Core
    • Labels:
      None
    • Environment:
      Windows 7 and Linux x86
    • Number of attachments :
      1

      Description

      When running the trader example, the story org/jbehave/examples/trader/stories/failure_followed_by_given_stories.story
      generates an invalid XML file by not including a final closing "story" tag. Attached is the generated invalid XML file.

        Activity

        Hide
        Alan Parkinson added a comment -

        After some research I have concluded this is actually caused by JBEHAVE-397 and the patch for this issue fixes this observed problem

        Show
        Alan Parkinson added a comment - After some research I have concluded this is actually caused by JBEHAVE-397 and the patch for this issue fixes this observed problem
        Mauro Talevi made changes -
        Field Original Value New Value
        Fix Version/s 3.2 [ 16757 ]
        Hide
        Mauro Talevi added a comment -

        Duplicate of JBEHAVE-397.

        Show
        Mauro Talevi added a comment - Duplicate of JBEHAVE-397 .
        Mauro Talevi made changes -
        Status Open [ 1 ] Resolved [ 5 ]
        Resolution Duplicate [ 3 ]

          People

          • Assignee:
            Unassigned
            Reporter:
            Alan Parkinson
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: