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

Pete pfein at pobox.com
Tue Sep 16 13:34:12 PDT 2008

On Sep 16, 2008, at 3:07 PM, Jesse Noller wrote:
>> What about fixture data though?  That can easily get larger than the
>> size of the rest of your distribution...
> Why not generate the fixture data on the fly though? For example, you
> can easily generate file data on the fly (that will always be the
> same) each time a test is run - I do this with file sizes ranging from
> 1 mb to 100s of gigabytes. This way I don't need to check in test
> data, or store it. I just generate it from the ether. The same applies
> to database/fixture data - why not generate it from some seed/ID on
> the fly?

Because I need to know what's in the data so that I can verify that  
full text queries against it return the correct results. How do you  
make sure your code is giving you the right output if you're feeding  
it random input?  Makes no sense to me...


More information about the testing-in-python mailing list