cryptonas/cryptonas-branches
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

added all non-code changes between r281 and r300 to the new release candidate

Browse source
This commit is contained in:
lars 2005-10-17 14:36:12 +00:00
parent 3cad3c5ae8
commit 7260c63d86
107 changed files with 5526 additions and 4016 deletions
Download patch file Download diff file Expand all files Collapse all files

123
v0.2.1/cbox-tree.d/_offline/doc/en/CryptoBoxDevValidation.html
View file

@ -29,62 +29,83 @@
<div id="doc">
<a id="top"></a>
<div class="wikipage">
<div id="searchable"><p>
<div class='wiki-toc'>
<h4>Table of Contents</h4>
<ol>
<li>
<a href="#head-5e20146fd39363329427c6251209cccb8d374f3e">Overview</a>
</li>
<li>
<a href="#head-6e1d416048c4d8ebfb5b3919b4d924c77e652a7b">Validate</a>
</li>
<li>
<a href="#head-5634566bd24f83d397b43525fc62685f6e678fbf">How to create a test</a>
</li>
<li><a href="CryptoBoxDevValidation.html#Overview">Overview</a></li>
<li><a href="CryptoBoxDevValidation.html#Validate">Validate</a></li>
<li><a href="CryptoBoxDevValidation.html#Howtocreateatest">How to create a test</a></li>
<li><a href="CryptoBoxDevValidation.html#Comments">Comments</a></li>
</ol>
<p> </p>
<hr>
<p> </p>
<p><em>back to <a href="CryptoBoxDev.html">CryptoBoxDev</a></em> </p>
</div>
<h2 id="head-5e20146fd39363329427c6251209cccb8d374f3e">Overview</h2>
</p>
<p>
<strong>Navigation:</strong> ( <a href="CryptoBoxDev.html">CryptoBoxDev</a>)
<p>The validation feature allows to check the programming logic of the <a href="CryptoBox.html">CryptoBox</a>. A lot of test cases are defined to test as many functions of the <a href="CryptoBox.html">CryptoBox</a> as possible. </p>
<p>The requests are processed with <a class="external" href="http://curl.haxx.se/">curl</a>. </p>
<p>The received web page is saved to allow a later design review or css debugging. </p>
<p>The current state of the <a href="CryptoBox.html">CryptoBox</a> is represented by ten single values (e.g.: <em>box is configured</em>, <em>IP of the box</em>, <em>current language setting</em>, ...), which are invisibly a part of each html page (as comments). The returned status of every request is compared to the predicted value of the test case. </p>
<p>Similar test cases are pooled into test groups (e.g.: <em>initialization</em>, <em>configuration</em> and <em>mounting</em>). </p>
<h2 id="head-6e1d416048c4d8ebfb5b3919b4d924c77e652a7b">Validate</h2>
<p>Run <tt>scripts/validate.sh&nbsp;check_all</tt> to conduct all tests of all groups. See <tt>scripts/validate.sh&nbsp;help</tt> for other actions. </p>
<p>The results will be saved in <em>validation/report</em>. </p>
<p>In addition to every single retrieved page, a html page called <em>summary.html</em> is created, which contains the state checks of all tests in a group. </p>
<h2 id="head-5634566bd24f83d397b43525fc62685f6e678fbf">How to create a test</h2>
<p>All test cases can be found in <em>validation/test-cases</em>. </p>
<p>Every test consists of: </p>
<dl>
<dt>input.curl</dt>
<dd><p>the configuration file for the <em>curl</em> request </p>
</dd>
<dt>output</dt>
<dd><p>the predicted state of the <a href="CryptoBox.html">CryptoBox</a> after the call </p>
</dd>
<dt>description</dt>
<dd><p>a short description of the test (will be used for the summary) </p>
</dd>
<dt>delay</dt>
<dd><p>[optional] time to wait after this test </p>
</dd>
</dl>
<p>Use the existing test cases as templates for new tests. </p>
<p>Any logical path of the web interface CGI should be validated by a test case. </p>
</p>
<hr />
<h1 id="ValidationoftheCryptoBox">Validation of the CryptoBox</h1>
<h2 id="Overview">Overview</h2>
<p>
The validation feature helps you to check the programming logic of the <a href="CryptoBox.html">CryptoBox</a>. A lot of test cases are defined to verify as many functions of the <a href="CryptoBox.html">CryptoBox</a> as possible.
</p>
<p>
The requests are processed with <a class="ext-link" title="http://curl.haxx.se/" href="http://curl.haxx.se/">curl</a>.
</p>
<p>
The received web page is saved to allow a later design review or css debugging.
</p>
<p>
The current state of the <a href="CryptoBox.html">CryptoBox</a> is represented by ten single values (e.g.: <i>box is configured</i>, <i>IP of the box</i>, <i>current language setting</i>, ...), which are invisibly a part of each html page (as comments). The returned status of every request is compared to the predicted value of the test case.
</p>
<p>
Similar test cases are pooled into test groups (e.g.: <i>initialization</i>, <i>configuration</i> and <i>mounting</i>).
</p>
<h2 id="Validate">Validate</h2>
<p>
Run <i><a href="/trac/cryptobox/browser/trunk/scripts/validate.sh">scripts/validate.sh</a>]</i> to conduct all tests of all groups. See <i>scripts/validate.sh help</i> for other actions.
</p>
<p>
The results will be saved in <i>validation/report</i>.
</p>
<p>
In addition to every single retrieved page, a html page called <i>summary-?.html</i> is created, which contains the state checks of all tests in a group.
</p>
<h2 id="Howtocreateatest">How to create a test</h2>
<p>
All test cases can be found in <i>validation/test-cases</i>.
</p>
<p>
Every test consists of the following files:
</p>
<table class="wiki">
<tr><td>input.curl</td><td>the configuration file for the <i>curl</i> request
</td></tr><tr><td>output</td><td>the predicted state of the <a href="CryptoBox.html">CryptoBox</a> after the call
</td></tr><tr><td>description</td><td>a short description of the test (will be used for the summary)
</td></tr><tr><td>delay</td><td>[optional] time to wait after this test
</td></tr></table>
<p>
Use the existing test cases as templates for new tests.
</p>
<p>
Read <a href="/trac/cryptobox/browser/trunk/validation/test-cases/README">validation/test-cases/README</a> for details.
</p>
<p>
Every logical path of the web interface CGI should be validated by a test case.
</p>
<hr />
<h2 id="Comments">Comments</h2>
<p>
</div>
</div>
</div><!-- end of 'words' -->
<div id="footer">