diff options
Diffstat (limited to 'third_party/java/proguard/proguard5.3.3/docs/quality.html')
| -rw-r--r-- | third_party/java/proguard/proguard5.3.3/docs/quality.html | 57 |
1 files changed, 57 insertions, 0 deletions
diff --git a/third_party/java/proguard/proguard5.3.3/docs/quality.html b/third_party/java/proguard/proguard5.3.3/docs/quality.html new file mode 100644 index 0000000000..5e85728417 --- /dev/null +++ b/third_party/java/proguard/proguard5.3.3/docs/quality.html @@ -0,0 +1,57 @@ +<!doctype html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> +<html> +<head> +<meta http-equiv="content-type" content="text/html; charset=iso-8859-1"> +<meta http-equiv="content-style-type" content="text/css"> +<link rel="stylesheet" type="text/css" href="style.css"> +<title>ProGuard Quality</title> +</head> +<body> + +<script type="text/javascript" language="JavaScript"> +<!-- +if (window.self==window.top) + document.write('<a class="largebutton" target="_top" href="index.html#quality.html">ProGuard index</a> <a class="largebutton" target="_top" href="http://www.guardsquare.com/dexguard">DexGuard</a> <a class="largebutton" target="_top" href="http://www.guardsquare.com/">GuardSquare</a> <a class="largebutton" target="other" href="http://sourceforge.net/projects/proguard/">Sourceforge</a>') +//--> +</script> +<noscript> +<a class="largebutton" target="_top" href="index.html#quality.html">ProGuard index</a> +<a class="largebutton" target="_top" href="http://www.guardsquare.com/dexguard">DexGuard</a> +<a class="largebutton" target="_top" href="http://www.guardsquare.com/">GuardSquare</a> +<a class="largebutton" target="other" href="http://sourceforge.net/projects/proguard/">Sourceforge</a> +</noscript> + +<h2>Quality</h2> + +In order to get a feel for the quality of the <b>ProGuard</b> code, it is run +through a regular automatic build process. This process produces numerous +statistics on the source code, Java lint comments, Java documentation +comments, the Java documentation itself, html lint comments on the Java +documentation, spell checks, compilation results, an output jar, dead code +analysis, a shrunk and obfuscated jar (using ProGuard itself!), test runs with +memory and performance analyses, etc. Most analyses are produced using freely +available tools. The results are poured into a convenient set of web pages +using bash/sed/awk scripts. You're welcome to have a look at an uploaded +snapshot of one of these runs: +<p> +<center><a href="http://proguard.sourceforge.net/quality/" +target="other">Automated Code Analysis and Testing Pages</a> (at <a +href="http://sourceforge.net/projects/proguard/" +target="other">SourceForge</a>)</center> +<p> +The pages will appear in a new window, which you probably want to view at +full-screen size. +<p> + +In addition, <b>ProGuard</b> is tested against a constantly growing test suite +(more than 1800 tests at this time of writing). These small programs contain a +wide range of common and uncommon constructs, in order to detect any regression +problems as soon as possible. + +<hr /> +<address> +Copyright © 2002-2017 +<a target="other" href="http://www.lafortune.eu/">Eric Lafortune</a> @ <a target="top" href="http://www.guardsquare.com/">GuardSquare</a>. +</address> +</body> +</html> |