snapshot 1.0.0b2

--HG--
branch : trunk
This commit is contained in:
holger krekel 2009-06-19 12:19:59 +02:00
parent 629fe2151c
commit 6de02a7976
5 changed files with 15 additions and 10 deletions

View File

@ -1,4 +1,4 @@
$Id: CHANGELOG 65791 2009-06-16 16:23:18Z hpk $
$Id: CHANGELOG 65819 2009-06-18 18:09:57Z hpk $
Changes between 1.0.0b1 and 1.0.0b2
=============================================

View File

@ -6,8 +6,7 @@ XXX draft
Welcome to the 1.0.0 py lib release - a python library aiming
to support agile and test-driven development.
It passes tests against Linux, OSX and Win32, on Python
2.3, 2.4, 2.5 and 2.6.
It works with Linux, OSX and Win32, on Python 2.3, 2.4, 2.5 and 2.6.
Main API/Tool Features:

View File

@ -2,6 +2,8 @@
Downloading
==============
Latest Release: 1.0.0b2
"easy_install py"
===================================================

View File

@ -1,6 +1,8 @@
py lib: Main tools and APIs
===================================
Latest Release: 1.0.0b2
`py.test`_ write and deploy unit- and functional tests to multiple machines.
`py.execnet`_ rapidly deploy local or remote processes from your program.

View File

@ -8,11 +8,11 @@ py.test implements much of its functionality by calling `well specified
hooks`_. Python modules which contain such hook functions are called
plugins. Hook functions are discovered in ``conftest.py`` files or
in **named** plugins. ``conftest.py`` files are sometimes called "anonymous"
or "local" plugins if they contain hooks. They allow to write and distribute
some extensions along with the test suite or the application package easily.
Named plugins are python modules or packages that have an all lowercase
``pytest_`` prefixed name and who are imported during tool startup or
the testing process.
or conftest plugins. They are useful for keeping test extensions close
to the application package. Named plugins are normal python modules or packages
that can be distributed separately. Named plugins need to follow a naming pattern;
they have an all lowercase ``pytest_`` prefixed name. While conftest plugins are
discovered automatically, named plugins must be explicitely specified.
.. _`tool startup`:
.. _`test tool starts up`:
@ -61,7 +61,7 @@ conftest.py as anonymous per-project plugins
--------------------------------------------------
The purpose of ``conftest.py`` files is to allow `project-specific
test configuration`_. But they also make for a good place to implement
test configuration`_. They thus make for a good place to implement
project-specific test related features through hooks. For example you may
set the `collect_ignore`_ variable depending on a command line option
by defining the following hook in a ``conftest.py`` file:
@ -91,7 +91,9 @@ reporting process. Upon loading of a plugin py.test performs
strict checking on contained hook functions. Function and argument names
need to match exactly one of `hook definition specification`_. It thus
provides useful error reporting on mistyped hook or argument names
and minimizes version incompatibilites.
and minimizes version incompatibilites. Below you find some introductory
information on particular hooks. It's sensible to look at existing
plugins so see example usages and start off with your own plugin.
.. _`hook definition specification`: http://bitbucket.org/hpk42/py-trunk/src/tip/py/test/plugin/hookspec.py