This is a pre-production deployment of Warehouse, however changes made here WILL affect the production instance of PyPI.
Project Description
*********************************
B-Open AT Content Types for Plone
*********************************

.. contents::

- Home page: http://www.bopen.eu/open-source/bopen.atcontenttypes
- Code repository: http://github.com/bopen/bopen.atcontenttypes


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

Because add-on themes or products may remove or hide the login portlet, this test will use the login form that comes with plone.

>>> browser.open(portal_url + '/login_form')
>>> 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 ensure that we get the friendly logged-in message:

>>> "You are now logged in" in browser.contents
True

Finally, let's return to the front page of our site before continuing

>>> browser.open(portal_url)

-*- extra stuff goes here -*-

The RichFolder content type
===============================

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

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

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

Now we fill the form and submit it.

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

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

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

We check that the changes were applied.

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

Removing a/an RichFolder content item
--------------------------------

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

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

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

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

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

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

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

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

Now we fill the form and submit it.

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

Done! We added a new RichFolder content item logged in as contributor.

Finally, let's login back as manager.

>>> browser.getLink('Log out').click()
>>> browser.open(portal_url + '/login_form')
>>> 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)
Release History

Release History

0.1

This version

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

Download Files

Download Files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

File Name & Checksum SHA256 Checksum Help Version File Type Upload Date
bopen.atcontenttypes-0.1-py2.4.egg (33.4 kB) Copy SHA256 Checksum SHA256 2.4 Egg Sep 7, 2010
bopen.atcontenttypes-0.1-py2.6.egg (33.4 kB) Copy SHA256 Checksum SHA256 2.6 Egg Sep 7, 2010

Supported By

WebFaction WebFaction Technical Writing Elastic Elastic Search Pingdom Pingdom Monitoring Dyn Dyn DNS Sentry Sentry Error Logging CloudAMQP CloudAMQP RabbitMQ Heroku Heroku PaaS Kabu Creative Kabu Creative UX & Design Fastly Fastly CDN DigiCert DigiCert EV Certificate Rackspace Rackspace Cloud Servers DreamHost DreamHost Log Hosting