#include "include/layout.wml" Classpath::Testing

The test framework for GNU Classpath is called . There are instructions within the Mauve website on how to download and use Mauve. Writing Mauve tests is the most important thing GNU Classpath developers could do for the project at this time.

Java API compatibility testing can be performed using . Japitools already does full API comparisons but it doesn't have the capability to extract APIs from the documentation - instead, the "japize" tool uses the jode.bytecode library to identify the public members of a given set of packages from the binary jars or zips. But japitools does separate the API-inspection phase ("japize") from the compatibility-testing phase ("japicompat") so it would be easy to offer an alternative to japize that worked on API documentation.

Another method of API compatibility testing is to use , at least until this functionality is merged into japitools. Classpath::Benchmarks Many free benchmarks are available. Benchmarks are a good way to test the functionality of a VM and at the same time get results that can be compared.
NameDescription
The Ashes benchmark