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

ALM Upload should use JUnit <system-out> and <system-err> data

      Hello,
      the ALM Plugin should support/upload the JUnit <system-out> and <system-err> data used in the <testcase ...> </testcase>. The very useful data is available since several years but not used/handled by the QC.

      The data should added in the QC to the "Test Lab", "Test Instance Details" "Attachments"
      or to the "Run Details" "Comments" or "Attachments".

      A suggestion only,
      with regards,
      Lutz

      p.s.

      Some JUnit information available from https://stackoverflow.com/questions/4922867/what-is-the-junit-xml-format-specification-that-hudson-supports/4925847

       

          [JENKINS-68891] ALM Upload should use JUnit <system-out> and <system-err> data

          Lutz Mader added a comment -

          Lutz Mader added a comment - And some more JUnit information are available from https://github.com/junit-team/junit5/blob/main/platform-tests/src/test/resources/jenkins-junit.xsd  

          Lutz Mader added a comment - - edited

          Hello,
          as far as I understand your code and the messages (see below) created by the plugin the AntJUnitReportParserImpl is used to parse my JUnit report file.
          Therefore a question of understanding, where to find the used field mapping used by AntJUnitReportParserImpl.
          I would like to check if the used fields have been removed in the QC, but I cannot find the assignment.

          Thanks for any help,
          Lutz

          Appendage:

          17:53:31 Recording test results
          17:53:31 [Checks API] No suitable checks publisher found.
          17:53:31 INFO: 'Upload test result to ALM' Post Build Step is being invoked by q-was-alm.
          17:53:31 INFO: 1 test result file found.
          17:53:31 INFO: Start to upload /usd/as98765a/work/jenkins/jobs/Introscope/jobs/agent_java-alm/builds/13/results_junit.xml
          17:53:31 INFO: Start to parse file: /usd/as98765a/work/jenkins/jobs/Introscope/jobs/agent_java-alm/builds/13/results_junit.xml
          17:53:31 Failed to parse file with: com.microfocus.application.automation.tools.results.parser.jenkinsjunit.JenkinsJUnitReportParserImpl
          17:53:31 Failed to parse file with: com.microfocus.application.automation.tools.results.parser.mavensurefire.MavenSureFireReportParserImpl
          17:53:31 Failed to parse file with: com.microfocus.application.automation.tools.results.parser.testngxml.TestNGXmlReportParserImpl
          17:53:32 Failed to parse file with: com.microfocus.application.automation.tools.results.parser.nunit3.NUnit3ReportParserImpl
          17:53:32 Failed to parse file with: com.microfocus.application.automation.tools.results.parser.nunit.NUnitReportParserImpl
          17:53:32 INFO: parse resut file succeed.
          17:53:32 INFO: Start to login to ALM Server.
          17:53:32 Start login to ALM server...
          17:53:32 User q-was-alm unauthorized.
          17:53:32 Got authenticate point:https://qualitycenter.intern:0/qcbin/authentication-point/authenticate
          17:53:32 Authenticate point schema or port is different with server's. Please check with ALM site admin.
          17:53:32 Try to authenticate through: https://qualitycenter.intern/qcbin/authentication-point/authenticate
          17:53:32 Logged in successfully to ALM Server https://qualitycenter.intern/qcbin/ using q-was-alm
          17:53:32 Creating session...
          17:53:32 Session created.
          17:53:32 INFO: Checking test folder...
          17:53:32 INFO: Checking testset folder...
          17:53:32 INFO: Uploading ALM Entities...
          17:53:34 INFO: Uploaded /usd/as98765a/work/jenkins/jobs/Introscope/jobs/agent_java-alm/builds/13/results_junit.xml.
          17:53:34 INFO: 'Upload test result to ALM' Completed.
          17:53:34 [lockable-resources] released lock on [INTROSCOPE_ALM, INTROSCOPE_JAVA]
          17:53:34 Finished: SUCCESS
          

          Lutz Mader added a comment - - edited Hello, as far as I understand your code and the messages (see below) created by the plugin the AntJUnitReportParserImpl is used to parse my JUnit report file. Therefore a question of understanding, where to find the used field mapping used by AntJUnitReportParserImpl. I would like to check if the used fields have been removed in the QC, but I cannot find the assignment. Thanks for any help, Lutz Appendage: 17:53:31 Recording test results 17:53:31 [Checks API] No suitable checks publisher found. 17:53:31 INFO: 'Upload test result to ALM' Post Build Step is being invoked by q-was-alm. 17:53:31 INFO: 1 test result file found. 17:53:31 INFO: Start to upload /usd/as98765a/work/jenkins/jobs/Introscope/jobs/agent_java-alm/builds/13/results_junit.xml 17:53:31 INFO: Start to parse file: /usd/as98765a/work/jenkins/jobs/Introscope/jobs/agent_java-alm/builds/13/results_junit.xml 17:53:31 Failed to parse file with: com.microfocus.application.automation.tools.results.parser.jenkinsjunit.JenkinsJUnitReportParserImpl 17:53:31 Failed to parse file with: com.microfocus.application.automation.tools.results.parser.mavensurefire.MavenSureFireReportParserImpl 17:53:31 Failed to parse file with: com.microfocus.application.automation.tools.results.parser.testngxml.TestNGXmlReportParserImpl 17:53:32 Failed to parse file with: com.microfocus.application.automation.tools.results.parser.nunit3.NUnit3ReportParserImpl 17:53:32 Failed to parse file with: com.microfocus.application.automation.tools.results.parser.nunit.NUnitReportParserImpl 17:53:32 INFO: parse resut file succeed. 17:53:32 INFO: Start to login to ALM Server. 17:53:32 Start login to ALM server... 17:53:32 User q-was-alm unauthorized. 17:53:32 Got authenticate point:https://qualitycenter.intern:0/qcbin/authentication-point/authenticate 17:53:32 Authenticate point schema or port is different with server's. Please check with ALM site admin. 17:53:32 Try to authenticate through: https://qualitycenter.intern/qcbin/authentication-point/authenticate 17:53:32 Logged in successfully to ALM Server https://qualitycenter.intern/qcbin/ using q-was-alm 17:53:32 Creating session... 17:53:32 Session created. 17:53:32 INFO: Checking test folder... 17:53:32 INFO: Checking testset folder... 17:53:32 INFO: Uploading ALM Entities... 17:53:34 INFO: Uploaded /usd/as98765a/work/jenkins/jobs/Introscope/jobs/agent_java-alm/builds/13/results_junit.xml. 17:53:34 INFO: 'Upload test result to ALM' Completed. 17:53:34 [lockable-resources] released lock on [INTROSCOPE_ALM, INTROSCOPE_JAVA] 17:53:34 Finished: SUCCESS

            ptofan Paul-Adrian Tofan
            lutzmad Lutz Mader
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: