Re: testing (was spambayes plugin, and other plugins)

Ryan Barrett wrote:
> On Sun, 9 Dec 2007, will wrote:
>> I don't know offhand how to go about testing plugins. PyBlosxom doesn't
>> provide any infrastructure for doing so. Is that something we should add and
>> if so, how should it work? That's a good subject for a 2.0 proposal.
> 
> you mean, a mock PyBlosxom? that would definitely be nice. there's probably a 
> lot of plugin code that could be tested without one, though, or with small, 
> trivial mocks of individual pieces. something like http://python-mock.sf.net/ 
> might get us even further.

I agree with you that plugins can be written in a way that doesn't 
require a MockBlosxom.

I was thinking more along the lines of writing a "good practices" guide 
for testing plugins in PyBlosxom that walks through where the test code 
should go, how to set up the tests, how to execute them and how to 
interact with PyBlosxom bits.

Additionally, if PyBlosxom had some infrastructure/API like the 
verification infrastructure/API where the user could do:

    pyblcmd testplugins

and PyBlosxom tests all the plugins that support the testing API--that'd 
be really useful.

/will

-------------------------------------------------------------------------
SF.Net email is sponsored by:
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php