Dead
[official-gcc.git] / gomp-20050608-branch / libjava / classpath / doc / www.gnu.org / benchmarks.wml
blob011cd57f7d7dd660a1c0d9003632e59634e09f00
1 #include "include/layout.wml"
3 <set-var last-modified-author="prk">
4 <subject "GNU Classpath Test and Benchmark Page">
6 <box>
7 <boxtitle><a name="testing">Classpath::Testing</a></boxtitle>
8 <boxitem>
9 <p>
10 The test framework for GNU Classpath is called
11 <createlink url="http://sources.redhat.com/mauve/" name="Mauve">. There
12 are instructions within the Mauve website on how to download and use Mauve.
13 Writing Mauve tests is the most important thing GNU Classpath developers
14 could do for the project at this time.
15 </p>
16 <p>
17 Java API compatibility testing can be performed using
18 <createlink url="http://www.kaffe.org/~stuart/japi/"
19 name="japitools">. Japitools already does
20 full API comparisons but it doesn't have the capability to extract
21 APIs from the documentation - instead, the "japize" tool uses the
22 jode.bytecode library to identify the public members of a given set of
23 packages from the binary jars or zips. But japitools does separate the
24 API-inspection phase ("japize") from the compatibility-testing phase
25 ("japicompat") so it would be easy to offer an alternative to japize
26 that worked on API documentation.
27 </p>
28 <p>
29 Another method of API compatibility testing is to use <createlink
30 url="http://majestix.ucnet.uoc.gr/~jgeorgal/pub/jdiff.sh"
31 name="jdiff.sh">, at least until this functionality is merged into
32 japitools.
33 </boxitem>
36 <boxtitle><a name="benchmarks">Classpath::Benchmarks</a></boxtitle>
37 <boxitem>
38 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.
40 <table border="0">
41 <tr>
42 <th>Name</th><th>Description</th>
43 </tr>
44 <tr>
45 <td><createlink name="Ashes" url="http://www.sable.mcgill.ca/ashes/"></td>
46 <td>The Ashes benchmark</td>
47 </tr>
48 </table>
49 </boxitem>
51 </box>