Skip to main content
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 (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 -*-


Contributors
************

Peter Dyson, Author


Download
********

Metadata

Release files for csci.feedback 1.0dev

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

Built distributions (wheels)

Table of built distributions (wheels) for csci.feedback 1.0dev
File Interpreter ABI Platform Actions
csci.feedback-1.1-py2.4.egg Legacy Egg format - - Details for csci.feedback-1.1-py2.4.egg
csci.feedback-1.0dev-py2.4.egg Legacy Egg format - - Details for csci.feedback-1.0dev-py2.4.egg

Total release size: 51.5 kB

Release files / csci.feedback-1.1-py2.4.egg

Download URL csci.feedback-1.1-py2.4.egg
Size 25.4 kB
Tags Egg
SHA-256 checksum
How to use checksums
b302a32e3a34c2895d84fa672ad87d3660b64a60b700e3bcda6725dbabf73c96
BLAKE2b-256 checksum
How to use checksums
f92d1c777a04c3555d90a29c37704405e3a0eabc8284c0979411dd7ed6990621
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No

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

Download URL csci.feedback-1.0dev-py2.4.egg
Size 26.1 kB
Tags Egg
SHA-256 checksum
How to use checksums
6f9b03301f99804f473ba44e96717429d51a2d62bcb452cd7663ecc8647da7ef
BLAKE2b-256 checksum
How to use checksums
2339b81fd616e5ee52ff58d5bb66e64295efd1efbcd9656298c963de55b5541a
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No

Security for csci.feedback 1.0dev

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