Welcome, guest | Sign In | My Account | Store | Cart

Notice! PyPM is being replaced with the ActiveState Platform, which enhances PyPM’s build and deploy capabilities. Create your free Platform account to download ActivePython or customize Python with the packages you require and get automatic updates.

Download
ActivePython

getpaid.pfgbuyableadapter is unavailable in PyPM, because there aren't any builds for it in the package repositories. Click the linked icons to find out why.

 Python 2.7Python 3.2Python 3.3
Windows (32-bit)
Windows (64-bit)
Mac OS X (10.5+)
Linux (32-bit)
Linux (64-bit)
 
Links
License
GPL
getpaid.pfgbuyableadapter
=========================
Change history
**************

Changelog
=========

1.0 (xxxx-xx-xx)
----------------

- Created recipe with ZopeSkel
  [""]

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 Buyable Form Adapter content type
===============================

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

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

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

Now we fill the form and submit it.

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

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

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

We check that the changes were applied.

    >>> 'Changes saved' in browser.contents
    True
    >>> 'New Buyable Form Adapter Sample' in browser.contents
    True

Removing a/an Buyable Form Adapter content item
--------------------------------

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

    >>> browser.open(portal_url)
    >>> 'New Buyable Form Adapter Sample' in browser.contents
    True

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

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

    >>> browser.open(portal_url)
    >>> 'New Buyable Form Adapter Sample' in browser.contents
    False

Adding a new Buyable Form Adapter content item as contributor
------------------------------------------------

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

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

Now we fill the form and submit it.

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

Done! We added a new Buyable Form Adapter 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)




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

"", Author


Download
********

Subscribe to package updates

What does the lock icon mean?

Builds marked with a lock icon are only available via PyPM to users with a current ActivePython Business Edition subscription.

Need custom builds or support?

ActivePython Enterprise Edition guarantees priority access to technical support, indemnification, expert consulting and quality-assured language builds.

Plan on re-distributing ActivePython?

Get re-distribution rights and eliminate legal risks with ActivePython OEM Edition.