Automated testing, a tenet of the buzzword-compliant "XP" Extreme Programming, can be seductively dangerous though. Beware, you will write tests first, but they clearly won't encompass the problem....or worse, you will write tests later and will unknowingly write tests that all pass. A good test suite is very difficult to build, and the need for manual testing can never be eliminated.
Far too often in the software industry does an emphasis on automated testing and formal test organizations (i.e. "testers by occuptation") result in poor manual unit testing. A developer really has to understand all of the corner cases before manually unit testing, and to write effective unit tests, he has to be even sharper.
Anyhow, be warned -- automated testing is great stuff -- but it is not a substitute for the real thing. Your test cases passing doesn't mean there are no bugs!
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|