Introduction
collective.betterbrowser improves the plone.testing browser with the following, run inside your functional testcase:
from collective.betterbrowser import new_browser
def test_all_the_things(self):
browser = new_browser(self.layer)
browser.login_admin()
browser.show()
At which point your default browser opens, showing the state of browser with the ability to actually interact with the testing plone site in the background.
Contributors
Denis Krienbuehl / href, Author
Changelog
0.4
Improves the flexibility of getting/setting a widget
0.3
Adds the ability to set/get widget values in a briefer form
0.2
Adds the ability to set date in addition to datetime [href]
0.1
Initial Release [href]
1 maintainer
Metadata
1 maintainer
Release files for collective.betterbrowser 0.4
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 |
|---|---|---|---|---|
| collective.betterbrowser-0.4.tar.gz | 5.5 kB | Without provenance | Details for collective.betterbrowser-0.4.tar.gz |
Release files / collective.betterbrowser-0.4.tar.gz
| Download URL | collective.betterbrowser-0.4.tar.gz |
|---|---|
| Size | 5.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
19c296c5bf0acc7c883293b0e762320da5a03926a1361808080c91dd37ab5a14
|
|
BLAKE2b-256 checksum How to use checksums |
80d7c90ced13fad613c1d4e56a1367c477a307f6aeedb1c400238dcca619d89b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for collective.betterbrowser 0.4
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.
