Fix spelling mistakes to force the Windows unit test box to cycle.
authordbaron@dbaron.org
Sat, 29 Sep 2007 17:49:57 -0700
changeset 6448 36454ccbfdab83f09a7d7b2fc5dc6a44eaa34792
parent 6447 693a6d9e10af594df39d6a1fd2f6ac8023fccdff
child 6449 9dba9f3eb72ca963222328716e7993373f650489
push idunknown
push userunknown
push dateunknown
milestone1.9a9pre
Fix spelling mistakes to force the Windows unit test box to cycle.
layout/doc/regression_tests.html
--- a/layout/doc/regression_tests.html
+++ b/layout/doc/regression_tests.html
@@ -47,17 +47,17 @@ pre.screen {display:table-cell}
 
 </head>
 <body>
 
 <h1>Table Regression Tests</h1>
 <h6>Bernd Mielke</h6>
 <h2>About This Document</h2>
 <p>
-This document describes my guerilla approach to successfully  running the table layout regression tests. It should encourage more people to run those tests.
+This document describes my guerrilla approach to successfully  running the table layout regression tests. It should encourage more people to run those tests.
 
 <h2>Subject Overview</h2>
 <p>
 The table element and its children are one of the major layout components that can create some structure on the screen. They are widely (ab)used  by page authors. Every small change in the table code can generate a bunch of bugzilla entries and a lot of seemingly unrelated dupes. With the high frequency of checkins in to the source tree  it is difficult and time consuming to track the regression down to a single checkin. The risk of becoming very infamous can be reduced by running the layout regression tests.
 
 <h2>Prerequisites</h2>
 <p>
 In order to run these tests, you will need to have:
@@ -79,21 +79,21 @@ In order to run these tests, you will ne
 <li>Make a note which tests have failed (these are  false positives. If you are in bad mood file a bug against Chris Waterson about them)
 <li>you can grep the failures by:<br>
 <code>grep 'rgd failed' &lt;outputfile.txt &gt;false_positive.txt</code> 
 <li> Make a copy of <code>gklayout.dll</code> and <code>gkcontent.dll</code> in the <code>dist</code> directory. If you would like to switch back, you will need them.
 <li>Make your changes to the source, compile and install.
 <li>execute in the <code>layout/html/tests/block</code>  directory <code>rtest.sh verify &gt;regression.txt</code>
 <li>Check how many tests have failed and analyse your results:
 <ul>
-<li>If the regression tests have failed at the same place as the previous diagnosted false positives =&gt; ignore
+<li>If the regression tests have failed at the same place as the previous diagnosed false positives =&gt; ignore
 <ol>
 <li>copy  <code>rtest.sh</code>  to <code>my_rtest.sh</code> 
 <li>create a new directory <code>my_files</code>. 
-<li>create in this diretory a file <code>file_list.txt</code>, where you put the url's of your remaining test failures
+<li>create in this directory a file <code>file_list.txt</code>, where you put the url's of your remaining test failures
 <li>change <code>my_rtest.sh</code> to use only directory <code>my_files</code>
 <li>go back to the original gklayout.dll and gkcontent.dll and repeat the regression test procedure on a much smaller set now.
 </ol>
 <li>Try to figure out what the other regressions are: Are they
      improving the picture or are they regressions?
 <li>Note the difficult to explain testfailures.
 </ul>
 <li> Change the source if necessary until the regression tests indicate that your patch does not hork the block and table layout
@@ -118,17 +118,17 @@ For every file in <code>file_list.txt</c
 <a href="http://lxr.mozilla.org/seamonkey/search?string=nsFrame%3A%3ADumpRegression">
 nsFrame::DumpRegression</a>.
 <p>
  The frame tree dumps are  invoked by the <code>-o</code> switch to the <code>viewer</code> (see <a href="http://lxr.mozilla.org/seamonkey/ident?i=PrintHelpInfo">commandline arguments </a>). 
 When <code>-o</code> is specified  together with a output directory for instance (<code>-o s:\mozilla\layout\html\tests\table\dom\</code>),  
 the frame trees are dumped to separate files in that directory for all URL's in <code>file_list.txt</code> (see: 
 <a href="http://lxr.mozilla.org/seamonkey/search?string=nsWebCrawler%3A%3ADumpRegression">
 nsWebCrawler::DumpRegressionData</a>) . 
-<p>Theire name is generated by replacing the old extension <code>.html</code> or <code>.xml</code> with <code>.rgd</code>.  For <code>file:///s|/mozilla/layout/html/tests/table/dom/appendCells1.html</code> a file <code>appendCells1.rgd</code> will be created in the <code>s:\mozilla\layout\html\tests\table\dom\</code> directory.
+<p>Their name is generated by replacing the old extension <code>.html</code> or <code>.xml</code> with <code>.rgd</code>.  For <code>file:///s|/mozilla/layout/html/tests/table/dom/appendCells1.html</code> a file <code>appendCells1.rgd</code> will be created in the <code>s:\mozilla\layout\html\tests\table\dom\</code> directory.
 
 <p>
  There is a special type of frame dumps - the printing regression tests, they are invoked by the <code>-Prt</code> command line argument to the <code>viewer</code> and include first a display then a frame dump taking into account the printer pages. A typical beginning of a dump (<code>*.rgd</code> file) looks like:<p>
 <pre class="screen">
 &lt;frame va="15022440" type="Viewport(-1)" state="270340" parent="0"&gt;
   &lt;view va="47171904"&gt;
   &lt;/view&gt;
   &lt;stylecontext va="15022232"&gt;