Show
Ignore:
Timestamp:
09/18/09 00:17:38 (15 years ago)
Author:
smidl
Message:

doc + updated tutorial

Files:
1 modified

Legend:

Unmodified
Added
Removed
  • library/doc/html/unit_testing.html

    r621 r632  
    5959    </ul> 
    6060  </div> 
    61   <div class="navpath"><a class="el" href="dev_guide2.html">Howto Contribute to BDM - Advanced development</a> 
     61  <div class="navpath"><a class="el" href="dev_guide2.html">BDM Development - Contribution guide</a> 
    6262  </div> 
    6363</div> 
     
    108108<p>Ideally, unit tests should test every method of every class (there are higher ideals, but they're even less realistic). Failing that, at least some methods of every class should be tested. Coverage tools (e.g. gcov) can show which parts of the library are not exercised by testsuite. </p> 
    109109</div> 
    110 <hr size="1"/><address style="text-align: right;"><small>Generated on Wed Sep 16 22:33:33 2009 for mixpp by&nbsp; 
     110<hr size="1"/><address style="text-align: right;"><small>Generated on Fri Sep 18 00:12:03 2009 for mixpp by&nbsp; 
    111111<a href="http://www.doxygen.org/index.html"> 
    112112<img class="footer" src="doxygen.png" alt="doxygen"/></a> 1.6.1 </small></address>