quality.html revision db267bc191f906f55eaef21a27110cce2ec57fdf 
1<!doctype html PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
2<html>
3<head>
4<meta http-equiv="content-type" content="text/html; charset=iso-8859-1">
5<meta http-equiv="content-style-type" content="text/css">
6<link rel="stylesheet" type="text/css" href="style.css">
7<title>ProGuard Quality</title>
8</head>
9<body>
10
11<h2>Quality</h2>
12
13In order to get a feel for the quality of the <b>ProGuard</b> code, it is run
14through a regular automatic build process. This process produces numerous
15statistics on the source code, Java lint comments, Java documentation
16comments, the Java documentation itself, html lint comments on the Java
17documentation, spell checks, compilation results, an output jar, dead code
18analysis, a shrunk and obfuscated jar (using ProGuard itself!), test runs with
19memory and performance analyses, etc. Most analyses are produced using freely
20available tools. The results are poured into a convenient set of web pages
21using bash/sed/awk scripts. You're welcome to have a look at an uploaded
22snapshot of one of these runs:
23<p>
24<center><a href="http://proguard.sourceforge.net/quality/"
25target="other">Automated Code Analysis and Testing Pages</a> (at <a
26href="http://sourceforge.net/projects/proguard/"
27target="other">SourceForge</a>)</center>
28<p>
29The pages will appear in a new window, which you probably want to view at
30full-screen size.
31<p>
32
33In addition, <b>ProGuard</b> is tested against a constantly growing test suite
34(more than 500 tests at this time of writing). These small programs contain a
35wide range of common and uncommon constructs, in order to detect any regression
36problems as soon as possible.
37
38<hr>
39<address>
40Copyright &copy; 2002-2009
41<a href="http://www.graphics.cornell.edu/~eric/">Eric Lafortune</a>.
42</address>
43</body>
44</html>
45