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

Recognize test results from com.github.searls:jasmine-maven-plugin

XMLWordPrintable

      jasmine-maven-plugin plugin is capable of outputting surefire/junit style reports: http://searls.github.com/jasmine-maven-plugin/

      While Jenkins will recognize jasmine-maven-plugin test results in a free-style(/freestyle) project, in a Maven project the results do not show. Free-style is nice, but then full Maven project functionality is not available, such as release and other goals.

      See jasmine-maven-plugin author searls comment here, quoted below:
      https://github.com/searls/jasmine-maven-plugin/issues/9

      "JUnit XML reports can only be specified by the user on freestyle projects. To get a maven2 project to see Jasmine's XML reports, SurefireArchiver would need to be updated to include the jasmine-maven-plugin's GAV."

      This issue is similar to JENKINS-11353. I expect it could be resolved, as searls suggests, in a similar manner. Looks like hudson.maven.reporters.SurefireArchiver would need to include registration for jasmine-maven-plugin.

          [JENKINS-13188] Recognize test results from com.github.searls:jasmine-maven-plugin

          Will Cain created issue -

          Will Cain added a comment -

          Example jasmine plugin configuration:

          <plugin>
  <groupId>com.github.searls</groupId>
  <artifactId>jasmine-maven-plugin</artifactId>
  <version>1.1.0</version>
  <executions>
    <execution>
      <goals>
        <goal>test</goal>
      </goals>
    </execution>
  </executions>
  <configuration>
    <jsSrcDir>${project.basedir}/src/main</jsSrcDir>
    <jsTestSrcDir>${project.basedir}/src/test</jsTestSrcDir>
    <junitXmlReportFileName>
    ../surefire-reports/TEST-jasmine.xml</junitXmlReportFileName>
    <sourceIncludes>
      <include>js/my.js</include>
    </sourceIncludes>
  </configuration>
</plugin>

          Will Cain added a comment - Example jasmine plugin configuration: <plugin> <groupId>com.github.searls</groupId> <artifactId>jasmine-maven-plugin</artifactId> <version>1.1.0</version> <executions> <execution> <goals> <goal>test</goal> </goals> </execution> </executions> <configuration> <jsSrcDir>${project.basedir}/src/main</jsSrcDir> <jsTestSrcDir>${project.basedir}/src/test</jsTestSrcDir> <junitXmlReportFileName> ../surefire-reports/TEST-jasmine.xml</junitXmlReportFileName> <sourceIncludes> <include>js/my.js</include> </sourceIncludes> </configuration> </plugin>

          Will Cain added a comment - - edited

          Here's a work-around I discovered while attempting to make the SurefireArchiver change. Turns out Jenkins will already notice jasmine-maven-plugin results when run through surefire-maven-plugin. You just have to tell surefire-maven-plugin explicitly to run test goal, preferably during package phase.

          For example:

                <plugin>
        <groupId>org.apache.maven.plugins</groupId>
        <artifactId>maven-surefire-plugin</artifactId>
        <version>2.12</version>
        <executions>
          <execution>
            <goals>
              <goal>test</goal>
            </goals>
            <!-- ensures surefire runs after jasmine: -->
            <phase>package</phase>
          </execution>
        </executions>
      </plugin>

          My testing demonstrate this indeed works. For me this greatly reduces the need for a Jenkins change.

          Will Cain added a comment - - edited Here's a work-around I discovered while attempting to make the SurefireArchiver change. Turns out Jenkins will already notice jasmine-maven-plugin results when run through surefire-maven-plugin. You just have to tell surefire-maven-plugin explicitly to run test goal, preferably during package phase. For example: <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-surefire-plugin</artifactId> <version>2.12</version> <executions> <execution> <goals> <goal>test</goal> </goals> <!-- ensures surefire runs after jasmine: --> <phase> package </phase> </execution> </executions> </plugin> My testing demonstrate this indeed works. For me this greatly reduces the need for a Jenkins change.
          Will Cain made changes -
          Priority Original: Major [ 3 ] New: Minor [ 4 ]

          Peter Davis added a comment - - edited

          I'd also love to see this fixed. In the meantime, I adapted Will Cain's workaround. I don't really like the JUnits to run during the "package" phase.

          Assuming there is a maven-surefire-plugin declared in your parent pom:

          <plugin>
	<groupId>com.github.searls</groupId>
	<artifactId>jasmine-maven-plugin</artifactId>
	<version>1.2.0.0</version>
...
</plugin>
<plugin>
	<artifactId>maven-surefire-plugin</artifactId>
	<executions>
		<execution>
			<!-- Ensure surefire runs after Jasmine.
			   - https://issues.jenkins-ci.org/browse/JENKINS-13188
			   - Maven plugins are run in the order specified in pom.xml, with inherited plugins first.
			   - So we must redefine the "test" goal's execution to be after Jasmine. -->
			<id>surefire-test</id>
			<phase>test</phase>
			<goals>
				<goal>test</goal>
			</goals>
			<configuration>
				<skipTests>${skipTests}</skipTests>
			</configuration>
		</execution>
	</executions>
	<configuration>
		<!-- Disable the default maven-surefire-plugin execution from parent pom. -->
		<skipTests>true</skipTests>
	</configuration>
</plugin>

          Edit: just pointing out you can do pretty much the same thing with maven-failsafe-plugin:integration-test as maven-surefire-plugin:test if needed.

          Peter Davis added a comment - - edited I'd also love to see this fixed. In the meantime, I adapted Will Cain's workaround. I don't really like the JUnits to run during the "package" phase. Assuming there is a maven-surefire-plugin declared in your parent pom: <plugin> <groupId> com.github.searls </groupId> <artifactId> jasmine-maven-plugin </artifactId> <version> 1.2.0.0 </version> ... </plugin> <plugin> <artifactId> maven-surefire-plugin </artifactId> <executions> <execution> <!-- Ensure surefire runs after Jasmine. - https://issues.jenkins-ci.org/browse/JENKINS-13188 - Maven plugins are run in the order specified in pom.xml, with inherited plugins first. - So we must redefine the "test" goal's execution to be after Jasmine. --> <id> surefire-test </id> <phase> test </phase> <goals> <goal> test </goal> </goals> <configuration> <skipTests> ${skipTests} </skipTests> </configuration> </execution> </executions> <configuration> <!-- Disable the default maven-surefire-plugin execution from parent pom. --> <skipTests> true </skipTests> </configuration> </plugin> Edit: just pointing out you can do pretty much the same thing with maven-failsafe-plugin:integration-test as maven-surefire-plugin:test if needed.

          Alexander Bertram added a comment - - edited

          This is a clever hack, will!

          But it would still be great to fix so this so that any maven plugin that produces junit-compatible xml will be consumed without having to muck around with plugin order.

          Is it possible for SurefireArchiver to search for tests after each module has finished? I am trying to get the renjin-maven-plugin:test goal working on Jenkins, which produces junit xml files from R-language tests, and it would be great to have it work out of the box.

          Alexander Bertram added a comment - - edited This is a clever hack, will! But it would still be great to fix so this so that any maven plugin that produces junit-compatible xml will be consumed without having to muck around with plugin order. Is it possible for SurefireArchiver to search for tests after each module has finished? I am trying to get the renjin-maven-plugin:test goal working on Jenkins, which produces junit xml files from R-language tests, and it would be great to have it work out of the box.
          kutzi made changes -
          Link New: This issue duplicates JENKINS-8334 [ JENKINS-8334 ]
          kutzi made changes -
          Link New: This issue is related to JENKINS-11353 [ JENKINS-11353 ]
          kutzi made changes -
          Resolution New: Duplicate [ 3 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]
          Jenkins IRC Bot made changes -
          Component/s New: maven-plugin [ 16033 ]
          Component/s Original: maven2 [ 15487 ]

            Unassigned Unassigned
            willcainsvg Will Cain
            Votes:
            2 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: