> I don't quite grasp "automated testing". And yes, I test in place
> constantly, but it only ever gets tedious when I cant figure out why
a
> thing doesn't work. ;)
Think about writing a moduule and testing it at the >>> prompt.
What you are doing is typing a series of python commands into
the
Hello Kent...
> I am a strong proponent of
> - incremental development
> - unit testing and test-first (or at least test-concurrent)
> programming - Don't Repeat Yourself and merciless refactoring
I see we have similarities. I purely hate having to rewrite something I've
already done once to sa
Hi Alan...
> Thats a great question, and I hope we get a few responses.
Me too!
Thank you for taking the time to reply.
Your response is far more complex than my original example, but its very
illustrative.
Not so much in what to do, but how to think about doing it, and that was my
goal.
Patric,
I am a strong proponent of
- incremental development
- unit testing and test-first (or at least test-concurrent) programming
- Don't Repeat Yourself and merciless refactoring
I look for a small piece of a problem, or a simplification of the problem, and write some code. I
write unit tests
Patric,
> How do you go about setting up a new application?
Thats a great question, and I hope we get a few responses.
> For example, suppose I need a script that will collect order
information
> for a set of items ona page. Its output will go to a mail program
so the
> artist can be notified.
Hi folks...
I was thinking about this the other day while prepping to write up
another CGI thing.
It occurred to me to wonder how other folks prepare an app, script,
whatever.
So the question is, and I am not looking for a "right answer" here. (I
doubt ther eis one, to be honest.)
How do you
