Probably not very well. At that time in my life/learning curve, testing usually consisted of running that portion of the app that used the code being changed, trying various things that the users would do and calling it good. Sometimes I would combine that with logging the imputs/outputs and intermediate values while running the app and the sift through the results to see if it did what I expected. In time I was able to create a test harness for some parts, but realistically, that kind of testing only seemed to work well for those pieces/parts could be isolated from everything else. Very ad-hock. Part of the problem was that almost everything (business rules, data access, etc.), as delivered, was buried in the GUI :-(.
-
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.
|