In <[email protected]>, on 02/10/2012
at 02:16 PM, Dave Day <[email protected]> said:
> I'd like to improve the quality of my code, before it goes out
>the door. Sometimes, some really stupid coding errors make it past
>my own testing. If your are writing the code, and then testing it
>yourself, you're kind of in a tunnel-vision scenario.
The best tools, IMHO, are
1. Code/design reviews
2. A thorough test suite. The hard part is not the driver for the
test, but coming up with the actual test data to cover all
code paths.
--
Shmuel (Seymour J.) Metz, SysProg and JOAT
ISO position; see <http://patriot.net/~shmuel/resume/brief.html>
We don't care. We don't have to care, we're Congress.
(S877: The Shut up and Eat Your spam act of 2003)
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
