alex23 schreef:
> On Jan 25, 5:44 am, Roel Schroeven <[EMAIL PROTECTED]>
> wrote:
>> I guess I just need to try somewhat harder to use TDD in my daily
>> coding. Apart from books, are there other resources that can help
>> beginners with TDD? Mailing lists, forums, newsgroups possibly?
>
> There's
On Jan 25, 5:44 am, Roel Schroeven <[EMAIL PROTECTED]>
wrote:
> I guess I just need to try somewhat harder to use TDD in my daily
> coding. Apart from books, are there other resources that can help
> beginners with TDD? Mailing lists, forums, newsgroups possibly?
There's the Testing-in-Python mail
Virgil Dupras schreef:
> On Jan 24, 1:30 pm, Roel Schroeven <[EMAIL PROTECTED]>
> wrote:
>> Virgil Dupras schreef:
>>
>>> I know what you mean by top-down vs. bottom-up and I used to have the
>>> same dilemma, but now I would tend to agree with Albert. Your issue
>>> with top-down or bottom-up is n
On Jan 24, 1:30 pm, Roel Schroeven <[EMAIL PROTECTED]>
wrote:
> Virgil Dupras schreef:
>
> > I know what you mean by top-down vs. bottom-up and I used to have the
> > same dilemma, but now I would tend to agree with Albert. Your issue
> > with top-down or bottom-up is not relevant in TDD. The only
Virgil Dupras schreef:
> I know what you mean by top-down vs. bottom-up and I used to have the
> same dilemma, but now I would tend to agree with Albert. Your issue
> with top-down or bottom-up is not relevant in TDD. The only thing that
> is relevant is to reach your current milestone as soon as p
On Jan 24, 7:37 am, [EMAIL PROTECTED] wrote:
> Hi
>
> Sorry if this is a bit off topic but as unit testing is such a
> cornerstone of python development I thought a few of you may be able
> to share your knowledge/experiences.
>
> I like the concept of TDD but find it difficult to put into practice
In article
<[EMAIL PROTECTED]>,
[EMAIL PROTECTED] wrote:
> So my question is when approaching a project that you want to employ
> test driven development on how and where do you start? And also if
> anyone uses top-down design with TDD I would be interested in how you
> do it (does it involve lo
On 2008-01-24, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> I like the concept of TDD but find it difficult to put into practice
> most of the time. I think this primarily because I tend to like top-
> down development and functional/object decomposition and TDD feels
> more like a bottom-up appr
On 1/24/08, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> Hi
>
> Sorry if this is a bit off topic but as unit testing is such a
> cornerstone of python development I thought a few of you may be able
> to share your knowledge/experiences.
Test driven development, simplistically, means to write the
(Joel, please preserve attribution lines on your quoted material so we
can see who wrote it.)
Joel Hedlund <[EMAIL PROTECTED]> writes:
> My presumption has been that in order to do proper test-driven
> development I would have to make enormous test suites covering all
> bases for my small hacks b
Diez B. Roggisch wrote:
> Sounds good to me. IMHO there are two ways one gathers tests:
>
> - concrete bugs appear, and one writes a test that reproduces the bug &
> eventually after the fix runs smoothly
>
> - new features are planned/implemented, and the tests accompany them right
> from the
> On Behalf Of Joel Hedlund
> My presumption has been that in order to do proper
> test-driven development I would have to make enormous test
> suites covering all bases for my small hacks before I could
> getting down and dirty with coding (as for example in
> http://www.diveintopython.org/uni
Joel Hedlund wrote:
>> test-driven development merely means that you take that test case and
>> *keep it* in your unit test. Then, once you're assured that you will
>> find the bug again any time it reappears, go ahead and fix it.
>
> My presumption has been that in order to do proper test-driven
> test-driven development merely means that you take that test case and
> *keep it* in your unit test. Then, once you're assured that you will
> find the bug again any time it reappears, go ahead and fix it.
My presumption has been that in order to do proper test-driven development I
would have t
Robert Kern <[EMAIL PROTECTED]> writes:
> Steven D'Aprano wrote:
> > Does anyone have generic advice for the testing and development of
> > this sort of function?
>
> "Design for Testability". In library code, never call the functions
> in the random module. Always take as an argument a random.Ran
Steven D'Aprano wrote:
> I'm working on some functions that, essentially, return randomly generated
> strings. Here's a basic example:
>
> def rstr():
> """Return a random string based on a pseudo
> normally-distributed random number.
> """
> x = 0.0
> for i in range(12):
>
16 matches
Mail list logo
