2 files were added to this release more than 14 days after its initial publication. Inspect the release files before installing.
This release is a pre-release and may not be stable for production use.
.. Note!
-----
Update the following URLs to point to your:
- code repository
- bug tracker
- questions/comments feedback mail
(do not set a real mail, to avoid spams)
Or remove it if not used.
- Code repository: http://svn.somewhere.com/...
- Questions and comments to somemailing_list
- Report bugs at http://bug.somewhere.com/..
Change history
**************
Changelog
=========
1.0 (xxxx-xx-xx)
----------------
- Created recipe with ZopeSkel
[Peter Dyson]
Detailed Documentation
**********************
Introduction
============
This is a full-blown functional test. The emphasis here is on testing what
the user may input and see, and the system is largely tested as a black box.
We use PloneTestCase to set up this test as well, so we have a full Plone site
to play with. We *can* inspect the state of the portal, e.g. using
self.portal and self.folder, but it is often frowned upon since you are not
treating the system as a black box. Also, if you, for example, log in or set
roles using calls like self.setRoles(), these are not reflected in the test
browser, which runs as a separate session.
Being a doctest, we can tell a story here.
First, we must perform some setup. We use the testbrowser that is shipped
with Five, as this provides proper Zope 2 integration. Most of the
documentation, though, is in the underlying zope.testbrower package.
>>> from Products.Five.testbrowser import Browser
>>> browser = Browser()
>>> portal_url = self.portal.absolute_url()
The following is useful when writing and debugging testbrowser tests. It lets
us see all error messages in the error_log.
>>> self.portal.error_log._ignored_exceptions = ()
With that in place, we can go to the portal front page and log in. We will
do this using the default user from PloneTestCase:
>>> from Products.PloneTestCase.setup import portal_owner, default_password
>>> browser.open(portal_url)
We have the login portlet, so let's use that.
>>> browser.getControl(name='__ac_name').value = portal_owner
>>> browser.getControl(name='__ac_password').value = default_password
>>> browser.getControl(name='submit').click()
Here, we set the value of the fields on the login form and then simulate a
submit click.
We then test that we are still on the portal front page:
>>> browser.url == portal_url
True
And we ensure that we get the friendly logged-in message:
>>> "You are now logged in" in browser.contents
True
-*- extra stuff goes here -*-
The countdown content type
===============================
In this section we are tesing the countdown content type by performing
basic operations like adding, updadating and deleting countdown content
items.
Adding a new countdown content item
--------------------------------
We use the 'Add new' menu to add a new content item.
>>> browser.getLink('Add new').click()
Then we select the type of item we want to add. In this case we select
'countdown' and click the 'Add' button to get to the add form.
>>> browser.getControl('countdown').click()
>>> browser.getControl(name='form.button.Add').click()
>>> 'countdown' in browser.contents
True
Now we fill the form and submit it.
>>> browser.getControl(name='title').value = 'countdown Sample'
>>> browser.getControl('Save').click()
>>> 'Changes saved' in browser.contents
True
And we are done! We added a new 'countdown' content item to the portal.
Updating an existing countdown content item
---------------------------------------
Let's click on the 'edit' tab and update the object attribute values.
>>> browser.getLink('Edit').click()
>>> browser.getControl(name='title').value = 'New countdown Sample'
>>> browser.getControl('Save').click()
We check that the changes were applied.
>>> 'Changes saved' in browser.contents
True
>>> 'New countdown Sample' in browser.contents
True
Removing a/an countdown content item
--------------------------------
If we go to the home page, we can see a tab with the 'New countdown
Sample' title in the global navigation tabs.
>>> browser.open(portal_url)
>>> 'New countdown Sample' in browser.contents
True
Now we are going to delete the 'New countdown Sample' object. First we
go to the contents tab and select the 'New countdown Sample' for
deletion.
>>> browser.getLink('Contents').click()
>>> browser.getControl('New countdown Sample').click()
We click on the 'Delete' button.
>>> browser.getControl('Delete').click()
>>> 'Item(s) deleted' in browser.contents
True
So, if we go back to the home page, there is no longer a 'New countdown
Sample' tab.
>>> browser.open(portal_url)
>>> 'New countdown Sample' in browser.contents
False
Adding a new countdown content item as contributor
------------------------------------------------
Not only site managers are allowed to add countdown content items, but
also site contributors.
Let's logout and then login as 'contributor', a portal member that has the
contributor role assigned.
>>> browser.getLink('Log out').click()
>>> browser.open(portal_url)
>>> browser.getControl(name='__ac_name').value = 'contributor'
>>> browser.getControl(name='__ac_password').value = default_password
>>> browser.getControl(name='submit').click()
>>> browser.open(portal_url)
We use the 'Add new' menu to add a new content item.
>>> browser.getLink('Add new').click()
We select 'countdown' and click the 'Add' button to get to the add form.
>>> browser.getControl('countdown').click()
>>> browser.getControl(name='form.button.Add').click()
>>> 'countdown' in browser.contents
True
Now we fill the form and submit it.
>>> browser.getControl(name='title').value = 'countdown Sample'
>>> browser.getControl('Save').click()
>>> 'Changes saved' in browser.contents
True
Done! We added a new countdown content item logged in as contributor.
Finally, let's login back as manager.
>>> browser.getLink('Log out').click()
>>> browser.open(portal_url)
>>> browser.getControl(name='__ac_name').value = portal_owner
>>> browser.getControl(name='__ac_password').value = default_password
>>> browser.getControl(name='submit').click()
>>> browser.open(portal_url)
Contributors
************
Peter Dyson, Author
Download
********
Metadata
Release files for csci.countdown 1.0dev
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Files added late
2 files were uploaded more than 14 days after the first file in this release.
While project maintainers occasionally add legitimate files to an existing release, late additions can also indicate a security compromise.
We recommend inspecting the release files before installing.
Built distributions (wheels)
| File | Actions Reset | |||
|---|---|---|---|---|
| csci.countdown-1.5dev-py2.4.egg | Legacy Egg format | - | - | Details for csci.countdown-1.5dev-py2.4.egg |
| csci.countdown-1.3dev-py2.4.egg | Legacy Egg format | - | - | Details for csci.countdown-1.3dev-py2.4.egg |
| csci.countdown-1.2dev-py2.4.egg | Legacy Egg format | - | - | Details for csci.countdown-1.2dev-py2.4.egg |
| csci.countdown-1.1dev-py2.4.egg | Legacy Egg format | - | - | Details for csci.countdown-1.1dev-py2.4.egg |
| csci.countdown-1.0dev-py2.4.egg | Legacy Egg format | - | - | Details for csci.countdown-1.0dev-py2.4.egg |
Total release size: 355.3 kB
Release files / csci.countdown-1.5dev-py2.4.egg
File added late
This file was uploaded more than 14 days after the first file in this release.
While project maintainers occasionally add legitimate files to an existing release, late additions can also indicate a security compromise.
We recommend inspecting the release file before installing.
| Download URL | csci.countdown-1.5dev-py2.4.egg |
|---|---|
| Size | 132.2 kB |
| Tags | Egg |
|
SHA-256 checksum How to use checksums |
56f7b3fcbf9aef26344ca6057055798dda3e2b8e304f84cf26a1b25e90aac3a6
|
|
BLAKE2b-256 checksum How to use checksums |
9a8828cdf75f8b1aa10c4d47db38d988cd9d1448e637e841967456672ecde5e8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / csci.countdown-1.3dev-py2.4.egg
File added late
This file was uploaded more than 14 days after the first file in this release.
While project maintainers occasionally add legitimate files to an existing release, late additions can also indicate a security compromise.
We recommend inspecting the release file before installing.
| Download URL | csci.countdown-1.3dev-py2.4.egg |
|---|---|
| Size | 132.1 kB |
| Tags | Egg |
|
SHA-256 checksum How to use checksums |
e62b3c315ece3caba29062c37ddd3338f81ab0557050eb0e2de5e4712178b05a
|
|
BLAKE2b-256 checksum How to use checksums |
d6bb5937e97b419538e7499d6c930b34640c9d3e8245c0dde518d564a5531f57
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / csci.countdown-1.2dev-py2.4.egg
| Download URL | csci.countdown-1.2dev-py2.4.egg |
|---|---|
| Size | 30.6 kB |
| Tags | Egg |
|
SHA-256 checksum How to use checksums |
c1ec7a61cf39534ab442097d9cfe311f9c62714af510e85c26da107a8cbae21b
|
|
BLAKE2b-256 checksum How to use checksums |
5f46e9b6d05702e26427ceffc5f3b63d38f3177918c5293b80abb7ce51516568
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / csci.countdown-1.1dev-py2.4.egg
| Download URL | csci.countdown-1.1dev-py2.4.egg |
|---|---|
| Size | 30.3 kB |
| Tags | Egg |
|
SHA-256 checksum How to use checksums |
fd77d689f542a19bb75611cfbc0fe1adbf87f5766de459f88dbcdb15e2bf3720
|
|
BLAKE2b-256 checksum How to use checksums |
72807e08c05abb7d8218fd66bfdabd12ae4804cacfa66b9f79c29fcd3a1fab42
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / csci.countdown-1.0dev-py2.4.egg
| Download URL | csci.countdown-1.0dev-py2.4.egg |
|---|---|
| Size | 30.2 kB |
| Tags | Egg |
|
SHA-256 checksum How to use checksums |
c59eb54e74afa5b6d8e5020a7b0f068e285f68fbf8682bed28baf59ffc8560f7
|
|
BLAKE2b-256 checksum How to use checksums |
bb244d5f8c5bd1e1be50910a6b49d27112274b18d85921ebeb353cd6e10e20fc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for csci.countdown 1.0dev
Upload timing
Release files added late
2 files were uploaded more than 14 days after the first file in this release.
While project maintainers occasionally add legitimate files to an existing release, late additions can also indicate a security compromise.
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.