Home | History | Annotate | Download | only in docs
      1 <!doctype html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//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 <script type="text/javascript" language="JavaScript">
      9 <!--
     10 if (window.self==window.top)
     11   window.top.location.replace("index.html#"+window.location.pathname+window.location.hash);
     12 else {
     13   var hash="#"+window.location.pathname.replace(window.top.location.pathname.replace("index.html", ""), "");
     14   if (window.top.location.hash!=hash)
     15     window.top.location.hash=hash;
     16 }
     17 //-->
     18 </script>
     19 </head>
     20 <body>
     21 
     22 <h2>Quality</h2>
     23 
     24 In order to get a feel for the quality of the <b>ProGuard</b> code, it is run
     25 through a regular automatic build process. This process produces numerous
     26 statistics on the source code, Java lint comments, Java documentation
     27 comments, the Java documentation itself, html lint comments on the Java
     28 documentation, spell checks, compilation results, an output jar, dead code
     29 analysis, a shrunk and obfuscated jar (using ProGuard itself!), test runs with
     30 memory and performance analyses, etc. Most analyses are produced using freely
     31 available tools. The results are poured into a convenient set of web pages
     32 using bash/sed/awk scripts. You're welcome to have a look at an uploaded
     33 snapshot of one of these runs:
     34 <p>
     35 <center><a href="http://proguard.sourceforge.net/quality/"
     36 target="other">Automated Code Analysis and Testing Pages</a> (at <a
     37 href="http://sourceforge.net/projects/proguard/"
     38 target="other">SourceForge</a>)</center>
     39 <p>
     40 The pages will appear in a new window, which you probably want to view at
     41 full-screen size.
     42 <p>
     43 
     44 In addition, <b>ProGuard</b> is tested against a constantly growing test suite
     45 (more than 900 tests at this time of writing). These small programs contain a
     46 wide range of common and uncommon constructs, in order to detect any regression
     47 problems as soon as possible.
     48 
     49 <hr />
     50 <noscript><div><a target="_top" href="index.html" class="button">Show menu</a></div></noscript>
     51 <address>
     52 Copyright &copy; 2002-2011
     53 <a target="other" href="http://www.lafortune.eu/">Eric Lafortune</a>.
     54 </address>
     55 </body>
     56 </html>
     57