collective.testing

Overview

general package for testing and debugging aids for CMF, Plone, Zope2 and Zope3

includes a layer for ZCML integratin testing

zcml for a default page for test objects (useful in zope 2.9)
postmortem helper:
>>> from collective.testing.debug import autopsy
>>> @autopsy
>>> def problem_func():
...     raise Exception('Trouble!')
some profiling tools

some logging and printing subscribers for zope.events

some fake response and request objects for zope

Metadata

Release files for collective.testing 0.3

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

Source distribution (sdist)

Source distribution for collective.testing 0.3
File	Size	Uploaded	Provenance	Actions
collective.testing-0.3.tar.gz	10.8 kB	May 1, 2007	Without provenance	Details for collective.testing-0.3.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for collective.testing 0.3
File	Interpreter	ABI	Platform	Actions Reset
collective.testing-0.3-py2.4.egg 15.9 kB May 1, 2007 Without provenance	Legacy Egg format	-	-	Details for collective.testing-0.3-py2.4.egg

Total release size: 26.7 kB

Release files / collective.testing-0.3.tar.gz

Download URL	collective.testing-0.3.tar.gz
Size	10.8 kB
Tags	Source
SHA-256 checksum How to use checksums	`17d00767356d003410b2e5cc7e70faba9b6e2f7d828c1d1ddb3bbefe21897d60`
BLAKE2b-256 checksum How to use checksums	`af18725964a00af6b6b8b9d0b18b9817763bec95c39e969cb698fa474a8896a2`
Upload date	May 1, 2007
Uploaded using Trusted Publishing? What is trusted publishing?	No

Release files / collective.testing-0.3-py2.4.egg

Download URL	collective.testing-0.3-py2.4.egg
Size	15.9 kB
Tags	Egg
SHA-256 checksum How to use checksums	`88f067955483c64a903cfc972c253fc991206ad913ee856ef2d607d87ae65885`
BLAKE2b-256 checksum How to use checksums	`14c88d13a2c1a68243895f2159c70da55ebe4c20b9c27ec1375cace93f0742cf`
Upload date	May 1, 2007
Uploaded using Trusted Publishing? What is trusted publishing?	No

Security for collective.testing 0.3

Report project as malware

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.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.