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

Display SYSOUT in the JUnit Report

XMLWordPrintable

    • Icon: Improvement Improvement
    • Resolution: Unresolved
    • Icon: Major Major
    • gallio-plugin
    • None

      SYSOUT is very important to me to understand why the test failed.
      Please display the SYSOUT during the transformation GALLIO=>JUNIT

      I already did that on a old version of the plugin's XSL, take a look at the attachment.

        1. gallio-1.0-to-junit-1.0.xsl
          7 kB
        2. gallio-report.xml
          242 kB

          [JENKINS-8845] Display SYSOUT in the JUnit Report

          Gregory Boissinot added a comment -

          Please could you add samples for testing the XSL?
          Thanks.

          Gregory Boissinot added a comment - Please could you add samples for testing the XSL? Thanks.

          Mathias Kluba added a comment -

          With my XSL, I can display sysout like this:

          http://178.170.124.134:8080/hudson/job/grozeille-spring-net-amqp/lastCompletedBuild/testReport/Spring.Erlang.Core/ErlangTemplateIntegrationTests/TestExecuteRpc/

          Mathias Kluba added a comment - With my XSL, I can display sysout like this: http://178.170.124.134:8080/hudson/job/grozeille-spring-net-amqp/lastCompletedBuild/testReport/Spring.Erlang.Core/ErlangTemplateIntegrationTests/TestExecuteRpc/

          Mathias Kluba added a comment -

          Example of Gallio with Sysout

          Mathias Kluba added a comment - Example of Gallio with Sysout

          Gregory Boissinot added a comment -

          Thank you for the XSL.
          Nevertheless, your current XSL breaks the existing unittests.
          With this XSL, the transformation is different.
          Could you look at the plugin
          git@github.com:jenkinsci/jsunit-plugin.git and adapt your XSL for the success of the existing unit tests.
          Thanks

          Gregory Boissinot added a comment - Thank you for the XSL. Nevertheless, your current XSL breaks the existing unittests. With this XSL, the transformation is different. Could you look at the plugin git@github.com:jenkinsci/jsunit-plugin.git and adapt your XSL for the success of the existing unit tests. Thanks

          Mathias Kluba added a comment - - edited

          It took the XSL from a old version of Gallio plugin.
          I changed it because I was not able to see my tests (because the old one didn't take care of the number of namespaces)

          You can just take the piece of my XSL to enhance the current one

          I'll do that when I have time.
          Regards.

          Mathias Kluba added a comment - - edited It took the XSL from a old version of Gallio plugin. I changed it because I was not able to see my tests (because the old one didn't take care of the number of namespaces) You can just take the piece of my XSL to enhance the current one I'll do that when I have time. Regards.

          Mathias Kluba added a comment -

          I assume you misspelled the URL we are talking about Gallio, not JSUnit: https://github.com/jenkinsci/gallio-plugin

          Mathias Kluba added a comment - I assume you misspelled the URL we are talking about Gallio, not JSUnit: https://github.com/jenkinsci/gallio-plugin

          Gregory Boissinot added a comment -

          @Mathias
          Any news?

          Gregory Boissinot added a comment - @Mathias Any news?

          Gregory Boissinot added a comment -

          Please upgrade the latest XSL in the current codebase with your changes.

          Gregory Boissinot added a comment - Please upgrade the latest XSL in the current codebase with your changes.

            gbois Gregory Boissinot
            grozeille Mathias Kluba
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: