Test harness for Hudson and plugins.
Unit test harness (src/main) and Unit tests for Hudson core (src/test).
Here is the list of declaration for hudson-test-harness. If you use Maven you can use the following code to add the dependency for this POM file.
<dependency> <groupId>org.jvnet.hudson.main</groupId> <artifactId>hudson-test-harness</artifactId> <version>1.318</version> </dependency>
If you think this Maven repository POM file listing for hudson-test-harness is inappropriate, such as containing malicious code/tools or violating the copyright, please email info at java2s dot com, thanks.
The hudson-test-harness-1.318 has 7 dependencies.The most popular ones are listed in the following table along with their categories and number of artifacts depending on them.
Category | Artifact | Depended By Count |
---|---|---|
Jetty | jetty 6.1.11 Jetty server core | 168 |
JUnit | htmlunit 2.2-hudson-10 A headless browser intended for use in testing web-based applications. | 18 |
JUnit | junit 3.8.1 JUnit is a regression testing framework written by Erich Gamma and Kent Beck. It is used by the developer who implements unit tests in Java. | 1966 |
Network | easymock 2.4 EasyMock provides an easy way to create Mock Objects for interfaces by generating them on the fly using Java's proxy mechanism | 181 |
The following plugins are used in the hudson-test-harness-1.318.jar
The following packages are defined in the hudson-test-harness-1.318.jar
org.jvnet.hudson.test org.jvnet.hudson.test.recipes org.jvnet.hudson.test.rhino
Here is the content of the POM file.
<?xml version="1.0"?> <!-- The MIT License Copyright (c) 2004-2009, Sun Microsystems, Inc., Kohsuke Kawaguchi Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. --> <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd"> <parent> <artifactId>pom</artifactId> <groupId>org.jvnet.hudson.main</groupId> <version>1.318</version> </parent> <modelVersion>4.0.0</modelVersion> <groupId>org.jvnet.hudson.main</groupId> <artifactId>hudson-test-harness</artifactId> <name>Test harness for Hudson and plugins</name> <description> Unit test harness (src/main) and Unit tests for Hudson core (src/test) </description> <build> <plugins> <plugin> <artifactId>maven-surefire-plugin</artifactId> <configuration> <!-- override with -DforkMode=pertest if you have "unable to create thread problems" on Windows --> <forkMode>once</forkMode> <!--<reportFormat>plain</reportFormat>--> <redirectTestOutputToFile>true</redirectTestOutputToFile> <systemProperties> <property> <!-- use AntClassLoader that supports predictable file handle release --> <name>hudson.ClassicPluginStrategy.useAntClassLoader</name> <value>true</value> </property> </systemProperties> </configuration> </plugin> <plugin> <groupId>org.codehaus.groovy.maven</groupId> <artifactId>gmaven-plugin</artifactId> <executions> <execution> <phase>process-resources</phase> <goals> <goal>execute</goal> </goals> <configuration> <source>${pom.basedir}/src/main/preset-data/package.groovy</source> </configuration> </execution> </executions> <dependencies> <dependency> <groupId>ant</groupId> <artifactId>ant</artifactId> <version>1.6.5</version> </dependency> </dependencies> </plugin> </plugins> </build> <dependencies> <dependency> <!-- put hudson.war in the classpath. we can't pull in the war artifact directly because Maven excludes all wars from classpath automatically. so we need a jar artifact. --> <groupId>${project.groupId}</groupId> <artifactId>hudson-war</artifactId> <version>${project.version}</version> <classifier>war-for-test</classifier> </dependency> <dependency> <groupId>${project.groupId}</groupId> <artifactId>maven-plugin</artifactId> <version>${project.version}</version> </dependency> <dependency> <groupId>${project.groupId}</groupId> <artifactId>maven-plugin</artifactId> <version>${project.version}</version> </dependency> <dependency> <groupId>org.mortbay.jetty</groupId> <artifactId>jetty</artifactId> <version>6.1.11</version> </dependency> <dependency> <groupId>org.jvnet.mock-javamail</groupId> <artifactId>mock-javamail</artifactId> <version>1.7</version> </dependency> <!--dependency> <groupId>org.openqa.selenium.client-drivers</groupId> <artifactId>selenium-java-client-driver</artifactId> <version>1.0-beta-1</version> </dependency--> <dependency> <groupId>org.jvnet.hudson</groupId> <artifactId>htmlunit</artifactId> <version>2.2-hudson-10</version> </dependency> <dependency><!-- temporary, until we bump to new htmlunit --> <groupId>org.jvnet.hudson</groupId> <artifactId>htmlunit-core-js</artifactId> <version>2.2-hudson-2</version> </dependency> <dependency> <!-- for testing JNLP launch. --> <groupId>org.jvnet.hudson</groupId> <artifactId>netx</artifactId> <version>0.5-hudson-2</version> </dependency> <dependency> <groupId>junit</groupId> <artifactId>junit</artifactId> <version>3.8.1</version> </dependency> <dependency> <groupId>org.easymock</groupId> <artifactId>easymock</artifactId> <version>2.4</version> </dependency> </dependencies> <profiles> <profile> <!-- Obtain code coverage report. This is done by running Unit tests on our own and suppressing surefire. --> <id>cobertura</id> <build> <plugins> <plugin> <groupId>org.kohsuke.gmaven</groupId> <artifactId>gmaven-plugin</artifactId> <executions> <!-- run unit test --> <execution> <phase>test</phase> <goals> <goal>execute</goal> </goals> <configuration> <scriptpath> <!-- load helpers from core --> <element>${project.basedir}/../core/src/build-script</element> </scriptpath> <source>${project.basedir}/src/build-script/unitTest.groovy</source> </configuration> </execution> </executions> </plugin> <plugin> <!-- unit tests are run by GMaven through Ant. --> <artifactId>maven-surefire-plugin</artifactId> <configuration> <skipTests>true</skipTests> </configuration> </plugin> </plugins> </build> </profile> </profiles> </project>