JBehave
  1. JBehave
  2. JBEHAVE-446

JBehave Reports import to Hudson xUnit Error: Conversion error Error to convert - A file not found

          Details

          • Type: Bug Bug
          • Status: Resolved Resolved
          • Priority: Major Major
          • Resolution: Fixed
          • Affects Version/s: 3.2
          • Fix Version/s: 3.4
          • Component/s: Hudson Support
          • Labels:
            None
          • Testcase included:
            yes
          • Number of attachments :
            1

            Description

            Hi,

            i know about some similar tasks JBEHAVE-394, but i think this does not resolve my problem.
            In my test project(see Attachment) i added a story(ist_produkt_in_bestand.story) with GivenStories. The report xml for that story is currupted because two end-tags are missing. </scenario></story>

            That failure takes place with version 3.1.2, 3.2-beta 1..5, 3.2 and 3.3-beta-1.

            I think it is realy possible that i doing something wrong with the configuration "src/test/java...jbehave.config.TraderEmbedderRunner". If it is, tell me pleace how i change it.

            My Hudson config:
            jbehave-hudson-plugin 3.2-beta-5
            xUnit 1.13

            Thanks for your help.

            Best regards

            Sven Schäfer

              Activity

              Mauro Talevi made changes -
              Field Original Value New Value
              Fix Version/s 3.4 [ 17278 ]
              Hide
              Permalink
              Mauro Talevi added a comment -

              Tested against 3.4-beta-4 and could not reproduce using the TraderJUnitRunner. The TraderEmbedderRunner looks a rather strange way to configure the stories and would not recommend it.

              Do note though that there is an issue with spaces in the given stories list, now fixed in JBEHAVE-512. If you remove spaces, it will work.

              Show
              Mauro Talevi added a comment - Tested against 3.4-beta-4 and could not reproduce using the TraderJUnitRunner. The TraderEmbedderRunner looks a rather strange way to configure the stories and would not recommend it. Do note though that there is an issue with spaces in the given stories list, now fixed in JBEHAVE-512 . If you remove spaces, it will work.
              Mauro Talevi made changes -
              Fix Version/s 3.x [ 16979 ]
              Fix Version/s 3.4 [ 17278 ]
              Hide
              Permalink
              Paul Hammant added a comment -

              This was fixed a couple of months ago. JBehave reports were writing (in some cases) XML that was missing closing tags.

              Show
              Paul Hammant added a comment - This was fixed a couple of months ago. JBehave reports were writing (in some cases) XML that was missing closing tags.
              Paul Hammant made changes -
              Status Open [ 1 ] Resolved [ 5 ]
              Resolution Fixed [ 1 ]
              Mauro Talevi made changes -
              Fix Version/s 3.4 [ 17278 ]
              Fix Version/s 3.x [ 16979 ]
              Hide
              Permalink
              Tidhar K.O. added a comment -

              Hi,
              i'm using JBehave 3.7.5 and this issue happens.
              there are some .xml files that don't have the closing tags, each time a different file.
              can I avoid it some how?

              thanks,
              Tizki

              Show
              Tidhar K.O. added a comment - Hi, i'm using JBehave 3.7.5 and this issue happens. there are some .xml files that don't have the closing tags, each time a different file. can I avoid it some how? thanks, Tizki
              Hide
              Permalink
              Mauro Talevi added a comment -

              Please provide an example project reproducing the problem and please create a new issue for it.

              Show
              Mauro Talevi added a comment - Please provide an example project reproducing the problem and please create a new issue for it.
              Hide
              Permalink
              Tidhar K.O. added a comment -

              Unfortunately I cannot share my project.
              But, this is an example for an xml that was created:

              <story path="stories/platform/packageB/packageC/packageD/storyName.story" title="">
              <meta>
              <property keyword="@" name="DEV:" value="dev one"/>
              <property keyword="@" name="DSL:" value="stepClassName1, stepClassName2, stepClassName3, stepClassName4"/>
              <property keyword="@" name="QA:" value="qa one"/>
              </meta>
              <scenario keyword="Scenario:" title="create entity lifecycle flow in X">
              <step outcome="successful">Given Y Service is up and running</step>
              <step outcome="successful">And X Service is up and running</step>
              <step outcome="successful">And Generate GUID for test story <parameter>storyName</parameter></step>
              <step outcome="successful">And Login user <parameter>adminUser</parameter> to the system</step>

              as you can see, the ending scenario and story tags are missing. that stats file is empty.
              perhaps the story stopped in the middle?

              let me know what other information can help, and i'll try to share it.

              thanks,
              Tizki

              Show
              Tidhar K.O. added a comment - Unfortunately I cannot share my project. But, this is an example for an xml that was created: <story path="stories/platform/packageB/packageC/packageD/storyName.story" title=""> <meta> <property keyword="@" name="DEV:" value="dev one"/> <property keyword="@" name="DSL:" value="stepClassName1, stepClassName2, stepClassName3, stepClassName4"/> <property keyword="@" name="QA:" value="qa one"/> </meta> <scenario keyword="Scenario:" title="create entity lifecycle flow in X"> <step outcome="successful">Given Y Service is up and running</step> <step outcome="successful">And X Service is up and running</step> <step outcome="successful">And Generate GUID for test story <parameter>storyName</parameter></step> <step outcome="successful">And Login user <parameter>adminUser</parameter> to the system</step> as you can see, the ending scenario and story tags are missing. that stats file is empty. perhaps the story stopped in the middle? let me know what other information can help, and i'll try to share it. thanks, Tizki

                People

                • Assignee:
                  Unassigned
                  Reporter:
                  Sven Schäfer
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  2 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: