Introduction
Provide useful base classes for testing in Plone.
Developed at Paradigma Internet [1].
TODO
Write tests.
Write documentation.
Changelog
0.0.6 (2011-06-24)
Added Plone 4.x compatibility.
0.0.5 (17dec2009)
Now requires prdg.plone.util>=0.0.6 because it made collective.wtf an optional dependency. Also removed the direct dependency on collective.wtf because it was non-sense.
0.0.4 (13ago2009)
Added new methods to FunctionalTestCase class.
Fixed a bug in ContentTypeTestCase.create_object(): object was being returned outside acquisition context. Fixed by using getattr instead of __getitem__.
0.0.3 (22jul2009)
Added collective.wtf as a dependency.
0.0.2 (26may2009)
Added functionality to InstallationTestCase to check for workflows.
Added WorkflowTestCase class.
Minor bug fixes.
0.0.1
Initial release
Metadata
Release files for prdg.plone.testing 0.0.6
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| prdg.plone.testing-0.0.6.zip | 11.4 kB | Without provenance | Details for prdg.plone.testing-0.0.6.zip |
Release files / prdg.plone.testing-0.0.6.zip
| Download URL | prdg.plone.testing-0.0.6.zip |
|---|---|
| Size | 11.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
24532c47c09c13b88b0837864d8485aa4ffe985dd3eec479f3428554e699b3b3
|
|
BLAKE2b-256 checksum How to use checksums |
28154268f67718a9963dc6d437eab99c788787c92268b529eab5ee1d215d5317
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for prdg.plone.testing 0.0.6
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.