Skip to main content
Release files added late

2 files were added to this release more than 14 days after its initial publication. Inspect the release files before installing.

Pre-release

This release is a pre-release and may not be stable for production use.

.. contents::

.. 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 (2009-10-22)
----------------
- Takes rss feeds and re-posts titles of articles to twitter feed and news
- 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 postfeed content type
===============================

In this section we are tesing the postfeed content type by performing
basic operations like adding, updadating and deleting postfeed content
items.

Adding a new postfeed 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
'postfeed' and click the 'Add' button to get to the add form.

>>> browser.getControl('postfeed').click()
>>> browser.getControl(name='form.button.Add').click()
>>> 'postfeed' in browser.contents
True

Now we fill the form and submit it.

>>> browser.getControl(name='title').value = 'postfeed Sample'
>>> browser.getControl('Save').click()
>>> 'Changes saved' in browser.contents
True

And we are done! We added a new 'postfeed' content item to the portal.

Updating an existing postfeed 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 postfeed Sample'
>>> browser.getControl('Save').click()

We check that the changes were applied.

>>> 'Changes saved' in browser.contents
True
>>> 'New postfeed Sample' in browser.contents
True

Removing a/an postfeed content item
--------------------------------

If we go to the home page, we can see a tab with the 'New postfeed
Sample' title in the global navigation tabs.

>>> browser.open(portal_url)
>>> 'New postfeed Sample' in browser.contents
True

Now we are going to delete the 'New postfeed Sample' object. First we
go to the contents tab and select the 'New postfeed Sample' for
deletion.

>>> browser.getLink('Contents').click()
>>> browser.getControl('New postfeed 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 postfeed
Sample' tab.

>>> browser.open(portal_url)
>>> 'New postfeed Sample' in browser.contents
False

Adding a new postfeed content item as contributor
------------------------------------------------

Not only site managers are allowed to add postfeed 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 'postfeed' and click the 'Add' button to get to the add form.

>>> browser.getControl('postfeed').click()
>>> browser.getControl(name='form.button.Add').click()
>>> 'postfeed' in browser.contents
True

Now we fill the form and submit it.

>>> browser.getControl(name='title').value = 'postfeed Sample'
>>> browser.getControl('Save').click()
>>> 'Changes saved' in browser.contents
True

Done! We added a new postfeed 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.postfeeds 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)

Table of built distributions (wheels) for csci.postfeeds 1.0dev
File Actions
csci.postfeeds-1.3dev-py2.4.egg Legacy Egg format - - Details for csci.postfeeds-1.3dev-py2.4.egg
csci.postfeeds-1.2dev-py2.4.egg Legacy Egg format - - Details for csci.postfeeds-1.2dev-py2.4.egg
csci.postfeeds-1.1dev-py2.4.egg Legacy Egg format - - Details for csci.postfeeds-1.1dev-py2.4.egg
csci.postfeeds-1.0dev-py2.4.egg Legacy Egg format - - Details for csci.postfeeds-1.0dev-py2.4.egg

Total release size: 545.8 kB

Release files / csci.postfeeds-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.postfeeds-1.3dev-py2.4.egg
Size 137.6 kB
Tags Egg
SHA-256 checksum
How to use checksums
8f1dce5a5d0bb9cd9c9d31e66db197d8033b4e3f0b1f88ebe3d895c3f1c24d19
BLAKE2b-256 checksum
How to use checksums
87a0400ea80a3610fa6ef7bd01e6a5b590aae656e9960e937e538e324461de0b
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No

Release files / csci.postfeeds-1.2dev-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.postfeeds-1.2dev-py2.4.egg
Size 137.6 kB
Tags Egg
SHA-256 checksum
How to use checksums
919c966d4a87d9d907bec8c560d393048f87a77d22e981c562270b570d541ff7
BLAKE2b-256 checksum
How to use checksums
096c185b870180b5afe3517130af2f40fa4bd95202514fffcb203f23aff84f0e
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No

Release files / csci.postfeeds-1.1dev-py2.4.egg

Download URL csci.postfeeds-1.1dev-py2.4.egg
Size 137.5 kB
Tags Egg
SHA-256 checksum
How to use checksums
982b4fc0955f21deadb83aa0ffc85dcb601ac26ded6cfada9bfe832b172ae35e
BLAKE2b-256 checksum
How to use checksums
15ac2099628ca949aabf0731a9aade7ffe0a566be13b49c7eb2f886a3be9b4a5
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No

Release files / csci.postfeeds-1.0dev-py2.4.egg

Download URL csci.postfeeds-1.0dev-py2.4.egg
Size 133.1 kB
Tags Egg
SHA-256 checksum
How to use checksums
c54b4e3adfd5114685cc6a5b82ef0a8bfc4683a45f4586b0bbbc4c1237cf86e3
BLAKE2b-256 checksum
How to use checksums
bbde63a513b35f7690997eafee21cd8c240d9d7901de4165ae202ad15aa15a47
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No

Security for csci.postfeeds 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.

Release history Release notifications | RSS feed

This release
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