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

Ryan Barrett wrote:
> On Fri, 7 Dec 2007, will wrote:
>> I picked nose (ha!) at the time after a cursory glance at the Python
>> testing world.  Since then, I'm pretty sure I'd like to stick with it.
> 
> i'm convinced. :P i'm all for unit tests, but i don't pay much attention to 
> the frameworks themselves. if you vote for nose, that's enough for me. i'll 
> remove the suggestion to switch.

I couldn't remember if we had talked about it or not.  It's kind of a 
bummer that we didn't--looks like I just picked nose on my own and 
started working on things.  I think I started writing test code in 2006, 
so it's been a while since then.

I'm not hung up on nose--if there are other frameworks that are more 
interesting, I'd be game for investigating.


I am going to introduce a task for increasing coverage of PyBlosxom for 
the next round of GHOP.  I've got it mostly worked out.  It's along the 
lines of this:

description = """
Progress on PyBlosxom 2.0 is moving along.  One of the things that is 
seriously hampering efforts is that very little of the codebase is 
covered by unit tests.

PyBlosxom uses nose to do unit test discovery.

The task here is to increase the test coverage to at least 60% for the 
code in PyBlosxom SVN trunk.

Things that could be tested for increasing test coverage:
   - Pyblosxom.pyblosxom.EnvironmentDict
   - Pyblosxom.pyblosxom.Request
   - Pyblosxom.pyblosxom.Response
   - Pyblosxom.pyblosxom.blosxom_entry_parser
   - Pyblosxom.tools.run_callback (there's some work on this already)
   - Pyblosxom.renderers.blosxom.get_included_flavour
   - Pyblosxom.renderers.blosxom.get_flavour_from_dir
   - Pyblosxom.renderers.blosxom.BlosxomRenderer


Completion:
   - a svn diff against the trunk
   - a list of coverage numbers before and after
   - a written explanation of what tests were added, any problems
     encountered, and any other observations that would help to
     improve testing for PyBlosxom in the future

Relevant pages:
   - HowToTest
"""

I figure we're at 36% or so now, so bumping us up to 60% coverage is a 
good jump.

How does that look?

Also, anyone can look at the GHOP tasks we've got in now:

http://code.google.com/p/google-highly-open-participation-psf/issues/list

Then search Open issues for "pyblosxom".

/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