[TIP] Python Testing book review

Jesse Noller jnoller at gmail.com
Sat Mar 6 11:07:59 PST 2010

On Sat, Mar 6, 2010 at 1:55 PM, C. Titus Brown <ctb at msu.edu> wrote:

>> However, in my experience Packt's books tend to suffer from some
>> pretty bad editing / checking. All it takes is a good reviewer to *run
>> the code* in the book. All of their books are feeling rushed, and I
>> feel bad for the authors, since it reflects on them.
> All it takes is a *good author* to run all the code in the book, first ;).
> I wrote some hacky little doctest-style code to make sure that the
> basic examples in my book worked.  Highly recommended approach.
> cheers,
> --titus
> --
> C. Titus Brown, ctb at msu.edu

And iPython + doctest mode is normally how I did testing of code when
tech reviewing :)

but; that's beside the point - you wrote a book? Was it on goatherding?

More information about the testing-in-python mailing list