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
********
.. 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
********
Release files for csci.images 1.0dev
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| csci.images-1.0dev-py2.4.egg | Legacy Egg format | - | - | Details |
Release files / csci.images-1.0dev-py2.4.egg
| Download URL | csci.images-1.0dev-py2.4.egg |
|---|---|
| Size | 26.2 kB |
| Tags | Egg |
|
SHA-256 checksum How to use checksums |
3e118cc000a78c7ed195c79d77302d48a63dbd271387c27256882fc850e4c26c
|
|
BLAKE2b-256 checksum How to use checksums |
6e73a66a895bdde42103e1c335f55a6ced177f856bb3fb0c1ee192c718f227d0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |