Skip to main content
https://github.com/zopefoundation/zc.recipe.testrunner/actions/workflows/tests.yml/badge.svg https://coveralls.io/repos/github/zopefoundation/zc.recipe.testrunner/badge.svg?branch=master Current version on PyPI Supported Python versions

This recipe generates zope.testing test-runner scripts for testing a collection of eggs.

Example usage in buildout.cfg:

[buildout]
parts = test

[test]
recipe = zc.recipe.testrunner
eggs = <eggs to test>

Change History

4.2.post1 (2026-08-20)

  • Republish after fixing Trusted Publishing integration.

4.2 (2026-08-20)

  • Support develop eggs installed as PEP 660 editable installs by zc.buildout >= 6: derive --test-path from the .pth file the editable install writes (or the project root recorded in direct_url.json) instead of the develop-eggs directory, in which no tests would be found. The test paths are additionally added to the sys.path of the generated script, so tests stay importable for editable installs which use an import hook instead of a plain path entry. (#26)

4.1.1 (2026-04-27)

  • Fix install() failing for egg specs with extras (e.g. pkg[test]) by stripping extras before canonicalizing the package name.

4.1 (2026-04-23)

  • Move package metadata from setup.py to pyproject.toml.

  • Add support for Python 3.14.

  • Drop support for Python 3.9.

  • Replace pkg_resources usage with importlib.metadata.

4.0 (2025-09-18)

  • Replace pkg_resources namespace with PEP 420 native namespace.

3.2 (2025-04-09)

  • If distribution is not found, try its canonical name.

  • If distribution is not found, explicitly show its name.

  • Add support for Python 3.13.

  • Drop support for Python 3.8.

3.1 (2024-09-27)

  • Add support for Python 3.12.

  • Drop support for Python 3.7.

  • Fix tests to run successfully against newer setuptools versions.

3.0 (2023-02-08)

  • Add support for Python 3.10, 3.11.

  • Drop support for Python 2.7, 3.5, 3.6.

2.2 (2020-11-30)

  • Add support for Python 3.9, PyPy2 and PyPy3.

2.1 (2019-05-14)

  • Add support for Python 3.5 up to 3.8a3.

2.0.0 (2013-02-10)

Work with buildout 2.

This was accomplised by starting from 1.3.0 then:

  • Merge fixes from 1.2.1 (svn://svn.zope.org/repos/main/zc.recipe.testrunner/tags/1.2.1) Excluding nailing zope.testing version. That fixes a bunch of windows issues

1.4.0 (2010-08-27)

  • Update to using zc.buildout 1.5.0 script generation. This adds the following options: include-site-packages, allowed-eggs-from-site-packages, extends, and exec-sitecustomize.

  • Merge fixes from 1.2.1 (svn://svn.zope.org/repos/main/zc.recipe.testrunner/tags/1.2.1) Excluding nailing zope.testing version. That fixes a bunch of windows issues

1.3.0 (2010-06-09)

  • Updated tests to run with the last versions of all modules.

  • Removed the usage of the deprecated zope.testing.doctest, therby also dropping Python 2.3 support.

  • Started using zope.testrunner instead of zope.testing.testrunner.

1.2.1 (2010-08-24)

  • Fixed a lot of windows issues

  • Nailed versions to ZTK 1.0a2 (oh well, we have to have at least some stability)

  • Fixed some other test failures that seemed to come from other packages

1.2.0 (2009-03-23)

  • Added a relative-paths option to use egg, test, and working-directory paths relative to the test script.

1.1.0 (2008-08-25)

  • Requiring at least zope.testing 3.6.0.

  • Fixed a bug: Parallel runs of layers failed when using working-directory parameter.

1.0.0 (2007-11-04)

  • Preparing stable release.

1.0.0b8 (2007-07-17)

  • Added the ability to use initialization option that will be inserted into the bin/test after the environment is set up.

1.0.0b7 (2007-04-26)

Feature Changes

  • Added optional option environment that allows defining a section in your buildout.cfg to specify environment variables that should be set before running the tests.

1.0.0b6 (2007-02-25)

Feature Changes

  • If the working directory is not specified, or specified as the empty string, an empty part directory is created for the tests to run in.

1.0.0b5 (2007-01-24)

Bugs fixed

  • When:

    • the working-directory option was used,

    • and the test runner needed to restart itself

    • and the test runner was run with a relative path (e.g. bin/test)

    then the testrunner could not restart itself successfully because the relative path in sys.argv[0] was no-longer valid.

    Now we convert sys.argv[0] to an absolute path.

1.0.0b4 (2006-10-24)

Feature Changes

  • Added a working-directoy option to specify a working directory for the generated script.

1.0.0b3 (2006-10-16)

Updated to work with (not get a warning from) zc.buildout 1.0.0b10.

1.0.0b2

Added a defaults option to specify testrunner default options.

1.0.0b1

Updated to work with zc.buildout 1.0.0b5.

1.0.0a3

Added a defaults option that lets you specify test-runner default options.

1.0.0a2

Now provide a extra-paths option for including extra paths in test scripts. This is useful when eggs depend on Python packages not packaged as eggs.

1.0.0a1

Initial public version

Release files for zc.recipe.testrunner 4.2.post1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for zc.recipe.testrunner 4.2.post1
File Size Uploaded
zc_recipe_testrunner-4.2.post1.tar.gz 20.0 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for zc.recipe.testrunner 4.2.post1
File Interpreter ABI Platform
zc_recipe_testrunner-4.2.post1-py3-none-any.whl Python 3 none any Details

Total release size: 36.6 kB

Release files / zc_recipe_testrunner-4.2.post1.tar.gz

Download URL zc_recipe_testrunner-4.2.post1.tar.gz
Size 20.0 kB
Tags Source
SHA-256 checksum
How to use checksums
cd180424b3a8bfeb5104d92d29d1b47fb5d53e45978af06517dd8425dab2b39d
BLAKE2b-256 checksum
How to use checksums
d2a6f9ef6c6534d90b2fbf958dc7e652a0b95de5eb32fdd91764715684694a30
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Aug 20, 2026.

Transparency log

Release files / zc_recipe_testrunner-4.2.post1-py3-none-any.whl

Download URL zc_recipe_testrunner-4.2.post1-py3-none-any.whl
Size 16.7 kB
Tags Python 3
SHA-256 checksum
How to use checksums
b72ee0262c89a6f41f9c7bb1450fee883f41377db33991fd2df833f5bbb65caa
BLAKE2b-256 checksum
How to use checksums
d2b1256bcfdea32f5502656965d081d332257b6de2886ac24a3f19d170d0ffd9
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Aug 20, 2026.

Transparency log
Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page