Tim 'tested-by-fire' Peters spoke:
> About a month ago, I tried something new: take those pricelesswhen i was writing an optics code last year i tried a similar but
> interactive testing sessions, paste them into docstrings, and write
> a module to do all the rest by magic
simpler version of this: when i first constructed the basics of a
module, i ran it and collected the results and pasted it in at the
bottom of the module file as comments. subsequent usage of the module
could use a checker() function which compared subsequent test output
with what was in the saved string of results, showing only changes
between one and the other.
i like your idea better for the reason that each example is located
as for interactive testing being the best mode, i agree for short
but for long winded code with many dependent pieces (a ray tracer
but i guess there is a whole art to figuring out at what granularity
<rant> finally, what i like best about your idea and design is that it
sometimes i tire so of clicking over to the browser to read the
nice work tim.....
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.