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