[py-dev] pytest news: plugins, pycon, release-separation
holger at merlinux.eu
Sat Feb 21 15:00:29 CET 2009
On Sat, Feb 21, 2009 at 14:22 +0100, Samuele Pedroni wrote:
> holger krekel wrote:
>> Hi folks,
>> some good news. as those glimpsing at pytest svn-commits know
>> i am heavily working on a new plugin architecture. I am
>> really happy about it as those also following me on my
>> brand-new twitter account (hpk42) might guess.
>> Around Pycon i am giving a tutorial about advanced testing
>> topics including cross-platform distributed testing and writing plugins
>> and i plan to talk in detil about the new and much improved ways of
>> doing things. Here is the status:
>> * Terminal reporting is now a nice self-contained plugin
>> * there is a new "xfail" plugin, inspired by SimPy to mark test
>> functions as "expected to fail" and report specially * a "poccoo"
>> plugin for sending test failures to http://paste.pocoo.org
>> * new plugins for managing setup/teardown of application state, using
>> a turns-out-to-work-great new mechanism which i guess nosetests might
>> imitate at some point :)
> Will plugins be able to customize/interact with collection or is that
> something that can only be done in conftests? I haven't looked deeply at
> the branch yet.
For starters, I prepared a plugin for collecting traditional unit tests:
notes on this:
* all the current plugins organise their code in a single file including tests.
* there currently is no defined hook for collecting files or
directories but it should be easy to add
> We are finally looking into open sourcing our (Open End) infrastructure
> browsers (more unit testing and integration testing than ui driving
> testing) through py.test and trying to cleanup some aspects of it; ways
> to control collection for special file extensions or for special base
> classes etc would be interesting.
great news. And a good case for using the plugin architecture.
More information about the Pytest-dev