[portland] Meeting notes: August 11, 2009 - optparse, and testing in a Python world
kirby.urner at gmail.com
Wed Aug 12 18:39:26 CEST 2009
My thanks to all as well, a really fine gathering.
In the interests of full disclosure, here's my blogged write-up, fair
warning in advance that it's really a splat against the wall of my
whole day, not tightly focused on our event:
I've incorporated quite a few links, including to your slides Adam,
and to Igal's write-up on this list.
If anyone has the patience to slog through it and finds something
egregiously wrong (from a technical standpoint), I'd happily make a
correction here and there.
I don't actually say much though, so I'm guessing we'll just let it
slide (I did manage to grab that "bug detector" picture -- pretty
On Wed, Aug 12, 2009 at 9:13 AM, Adam Lowry<adam at therobots.org> wrote:
> On Aug 11, 2009, at 8:35 PM, Igal Koshevoy wrote:
>> 2. Adam Lowry presented "Testing My Patience", discussing testing in
> Thanks for the write-up, Igal. My slides and a few notes are up:
> py.test is actually a more powerful tool than nose, in general, but I'd
> still recommend starting with nose.
> The other mocking library I mentioned is mocker:
> It works in the record->replay model, like Mox. It was harder for me to
> understand, but it might be better for you. It's also been around longer.
> The very simplest mock library is python-mock:
> Designing a system to handle your functional test setup can be troublesome,
> but I'm happy to help if I can.
> Portland mailing list
> Portland at python.org
More information about the Portland