My point being that asserts direct most programmers to copy and paste the same code that you should have used earlier on in your app to check if the card number was valid -- a regex or a sub -- whatever. This not only is redundant it also give the developer a false sense of a safety net (if his code did not verify the card correctly before it will/may not now). I think it is better to use a well established test harness to actually test a bad card number insert in multiple ways and verify the expected behavior happens. In my mind asserts are just as bad as mixing the display logic of web apps with the program logic -- in small apps just use print statements to debug or whatever you are comfortable with. In large complex apps do debugging and testing in specialized areas -- there is a reason it is called the debugger you know.
-
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.
|
