Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-20381

ResultSeeking Strategy "jUnit Suite Name" not working

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • testlink-plugin
    • None
    • Jenkins 1.516 on Debian

      We use CasperJS as Tool for Frontend Integrationtests. Casper generates jUnit-Files like this:

      <testsuites time="12.975">
      <testsuite name="/qa/src/test/javascript/portal/questionnaire/photoupload.js" tests="2" failures="0" errors="0" time="12.975" timestamp="2013-11-01T13:24:46.696Z" package="../../test/javascript/portal/questionnaire/photoupload">
      <testcase name="ProfilePrefill is openend" classname="../../test/javascript/portal/questionnaire/photoupload" time="10.292"/>
      <testcase name="ajaxTransport is defined" classname="../../test/javascript/portal/questionnaire/photoupload" time="0.001"/>

      <system-out/>
      </testsuite>
      </testsuites>

      The only way I see to get a mapping is via the ResultSeeking Strategy: "jUnit Suite Name".
      We use exactly the String that is entered in Testlinks "Custom Field"

      We also tried to use a simpler name="photoupload".

      Jenkins can read the jUnit File and shows the correct Result. But for Testlink "Execution Status" is set to "Not Run"

      We have other Backend jUnit Testfiles that do work for us. (At least with ResultSeeking "jUnit Method Name")

          [JENKINS-20381] ResultSeeking Strategy "jUnit Suite Name" not working

          Florian Weber created issue -
          Florian Weber made changes -
          Description Original: We use CasperJS as Tool for Frontend Integrationtests. Casper generates jUnit-Files like this:

          <testsuites time="12.975">
          <testsuite name="/qa/src/test/javascript/portal/questionnaire/photoupload.js" tests="2" failures="0" errors="0" time="12.975" timestamp="2013-11-01T13:24:46.696Z" package="../../test/javascript/portal/questionnaire/photoupload">
          <testcase name="ProfilePrefill is openend" classname="../../test/javascript/portal/questionnaire/photoupload" time="10.292"/>
          <testcase name="ajaxTransport is defined" classname="../../test/javascript/portal/questionnaire/photoupload" time="0.001"/>

          <system-out/>
          </testsuite>
          </testsuites>

          The only way I see to get a mapping is via the ResultSeeking Strategy: "jUnit Suite Name".
           We use exactly the String that is entered in Testlinks "Custom Field"

          We also tried to use a simpler name="photoupload".

          Jenkins can read the jUnit File and shows the correct Result. But for Testlink "Execution Status" is set to "Not Run"

          Maybe its a problem to have several testcase-Tags? CasperJS generates one testcase for every Assert :-/


          We have other Backend jUnit Testfiles that do work for us. (At least with ResultSeeking "jUnit Method Name")
          New: We use CasperJS as Tool for Frontend Integrationtests. Casper generates jUnit-Files like this:

          <testsuites time="12.975">
          <testsuite name="/qa/src/test/javascript/portal/questionnaire/photoupload.js" tests="2" failures="0" errors="0" time="12.975" timestamp="2013-11-01T13:24:46.696Z" package="../../test/javascript/portal/questionnaire/photoupload">
          <testcase name="ProfilePrefill is openend" classname="../../test/javascript/portal/questionnaire/photoupload" time="10.292"/>
          <testcase name="ajaxTransport is defined" classname="../../test/javascript/portal/questionnaire/photoupload" time="0.001"/>

          <system-out/>
          </testsuite>
          </testsuites>

          The only way I see to get a mapping is via the ResultSeeking Strategy: "jUnit Suite Name".
           We use exactly the String that is entered in Testlinks "Custom Field"

          We also tried to use a simpler name="photoupload".

          Jenkins can read the jUnit File and shows the correct Result. But for Testlink "Execution Status" is set to "Not Run"


          We have other Backend jUnit Testfiles that do work for us. (At least with ResultSeeking "jUnit Method Name")
          Florian Weber made changes -
          Summary Original: ResultSeeking Strategy not working for some jUnit Files New: ResultSeeking Strategy "jUnit Suite Name" not working
          Bruno P. Kinoshita made changes -
          Status Original: Open [ 1 ] New: In Progress [ 3 ]
          Bruno P. Kinoshita made changes -
          Status Original: In Progress [ 3 ] New: Open [ 1 ]
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 151905 ] New: JNJira + In-Review [ 178108 ]

            kinow Bruno P. Kinoshita
            fwebdev Florian Weber
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: