yuva2achieve / mb-unit

Automatically exported from code.google.com/p/mb-unit
1 stars 0 forks source link

Gallio should produce JUnit-format test report to provide better Bamboo integration #839

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Run Gallio on C# code to produce a test report (gallio-report.xml).
2. Configure Bamboo to recognize that the build has unit tests (and therefore 
produces a test report).

What is the expected output?
I expect that Bamboo would recognize that gallio-report.xml contains 
information about the unit tests that were performed.

What do you see instead?
Bamboo does not recognize that gallio-report.xml contains information about the 
unit tests that were performed (because at the time of writing Bamboo only 
recognizes test reports that are in JUnit format).

What version of the product are you using? On what operating system?
I am using Gallio 3.2.750.0 on Windows XP 2002 Service Pack 3.

Please provide any additional information below.
My build uses Maven.  As a workaround, I configure Maven to use the 
gallio-to-junit.xsl stylesheet (taken from 
http://code.google.com/p/mb-unit/issues/attachmentText?id=399&aid=-1714903327162
113860&name=gallio-to-junit.xsl&token=6e2598d0c211b63d6a91f10748878354) to 
convert gallio-report.xml from Gallio format to JUnit format:
      <plugin>
        <groupId>org.codehaus.mojo</groupId>
        <artifactId>xml-maven-plugin</artifactId>
        <executions>
          <execution>
            <id>gallio2junit</id>
            <phase>prepare-package</phase>
            <goals>
              <goal>transform</goal>
            </goals>
          </execution>
        </executions>
        <configuration>
          <transformationSets>
            <transformationSet>
              <dir>${project.build.directory}</dir>
              <includes>
                <include>gallio-report.xml</include>
              </includes>
              <stylesheet>src/main/gallio-to-junit.xsl</stylesheet>
              <outputDir>${project.build.directory}/test-reports</outputDir>
            </transformationSet>
          </transformationSets>
        </configuration>
      </plugin>

It's a pain that every C# project must duplicate this same workaround.  If 
Gallio produced JUnit-format test reports out-of-the-box, this duplication 
would not be necessary.

Original issue reported on code.google.com by blaney.k...@gmail.com on 9 May 2011 at 3:20

GoogleCodeExporter commented 9 years ago

Original comment by Yann.Tre...@gmail.com on 9 May 2011 at 6:50

GoogleCodeExporter commented 9 years ago

Original comment by Yann.Tre...@gmail.com on 14 Jun 2011 at 5:53