currently our test suite looks like this:
cd src; make score
PASSED AccessingSubstrings
PASSED TakeApart
PASSED IsNum
PASSED StringsDemo
PASSED TrimStr
PASSED ShuffleDeck52
PASSED IsNumStringDemo
PASSED A2s
PASSED Basename
PASSED DeShell
PASSED Factorial
PASSED Shellaa
which means we have test cases running, and passing, on the above.
fyi: a test engine function is any function starting with an
UpperCase- the test engine hunts those out in the source code, and
runs them.
note that if a test function is ugly, you can still add it to the
code but hide it from the web view by starting it with the right
number of blank spaces.
- three blanks: stuff to hide from the html but give to awk
- two blanks: stuff to convert to verbatim html and comment out from awk
- one blank: stuff to covert to verbatim html and give to awk
- zero blanks: stuff to covert to html and comment out from awk
t
--
there are those who call me... tim (menzies, ph.d.)
morgantown (39.6n, -79w), usa
assoc prof csee, wvu
http://menzies.us
1-304-376-2859
PROBLEM: Handling e-mail is very very very slow, resulting in inbox overflow.
SOLUTION: Adopt the "http://four.sentenc.es" policy: no responses
longer than 4 sentences. It’s that simple. Care to try it?