At any time, all the code in SVN should be compilable and should pass all the unit tests. There is no guarantee that it will be full featured - this is a work in progress.

Latest build

You can download the latest build from our Cruise Control server kindly hosted by Canoo AG .

Checking out SVN repository

Another way to get the latest code is through SVN. Create a directory for HtmlUnit (for instance c:\htmlunit or ~/htmlunit). Change to that directory and execute the following commands.

svn co https://htmlunit.svn.sourceforge.net/svnroot/htmlunit/trunk/htmlunit .
            

Compiling the code

The preferred way to build HtmlUnit is with maven 2 .

mvn compile

This will do an incremental compile of all the code.

mvn clean compile

This will do a clean compile of all the code.

Dependencies for IDE

Usually, you need to get the JARs for your IDE. You can do that by something like:

mvn eclipse:eclipse

or

mvn idea:idea

This will create appropriate IDE project. Note that HtmlUnit is mostly at the bleeding edge, to the extent that an HtmlUnit-local repository has been created to store snapshots of various dependencies.

Running the tests

All the tests are based on JUnit .

mvn test

This will force a recompile of the java classes if needed.

mvn test -Dtest=DomNodeTest

This will run only the specified test class.

Packaging

mvn package

In the project's target directory you'll able to see the generated jar file with the name "htmlunit-" followed by the version number.

mvn source:jar

This generates a source jar file.

mvn source:test-jar

This will generate a jar file of the test sources.