[TIP] why you should distribute tests with your application / module

Pete pfein at pobox.com
Wed Sep 17 10:45:37 PDT 2008

On Sep 17, 2008, at 12:14 PM, C. Titus Brown wrote:

> On Wed, Sep 17, 2008 at 11:56:35AM -0500, Pete wrote:
> -> I still maintain that there are situations where it's desirable/
> -> preferable to have real, static fixture data.  Here are a few more
> -> OTOMH: financial algorithms, image processing, regression tests of
> -> text parsing. Anyone have recommendations on best practices for  
> doing
> -> so (as opposed to continuing to tell me how to avoid the problem
> -> entirely)?  Thanks.
> I'm not sure what you mean by "best practices" -- for distribution of
> the data, or for finding it in the first place?

I mean for distribution.  My test dataset falls into some middle  
ground - it's a few megabytes. Not the gigabytes that would lean  
towards generation, but still larger than the rest of my source tree.   
Seems silly to turn a 30K package into a 5M one b/c of test data...

More information about the testing-in-python mailing list