Package: getpaid.pfgbuyableadapter
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 whatthe 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 siteto play with. We *can* inspect the state of the portal, e.g. usingself.portal and self.folder, but it is often frowned upon since you are nottreating the system as a black box. Also, if you, for example, log in or setroles using calls like self.setRoles(), these are not reflected in the testbrowser, 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 shippedwith Five, as this provides proper Zope 2 integration. Most of thedocumentation, 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 letsus 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 willdo this using the default user from PloneTestCase:>>> from Products.PloneTestCase.setup import portal_owner, default_passwordBecause 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 asubmit click.  We then ensure that we get the friendly logged-in message:>>> "You are now logged in" in browser.contentsTrueFinally, 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 performingbasic operations like adding, updadating and deleting Buyable Form Adapter contentitems.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.contentsTrueNow we fill the form and submit it.>>> browser.getControl(name='title').value = 'Buyable Form Adapter Sample'>>> browser.getControl('Save').click()>>> 'Changes saved' in browser.contentsTrueAnd 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.contentsTrue>>> 'New Buyable Form Adapter Sample' in browser.contentsTrueRemoving a/an Buyable Form Adapter content item--------------------------------If we go to the home page, we can see a tab with the 'New Buyable Form AdapterSample' title in the global navigation tabs.>>> browser.open(portal_url)>>> 'New Buyable Form Adapter Sample' in browser.contentsTrueNow we are going to delete the 'New Buyable Form Adapter Sample' object. First wego to the contents tab and select the 'New Buyable Form Adapter Sample' fordeletion.>>> 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.contentsTrueSo, if we go back to the home page, there is no longer a 'New Buyable Form AdapterSample' tab.>>> browser.open(portal_url)>>> 'New Buyable Form Adapter Sample' in browser.contentsFalseAdding a new Buyable Form Adapter content item as contributor------------------------------------------------Not only site managers are allowed to add Buyable Form Adapter content items, butalso site contributors.Let's logout and then login as 'contributor', a portal member that has thecontributor 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.contentsTrueNow we fill the form and submit it.>>> browser.getControl(name='title').value = 'Buyable Form Adapter Sample'>>> browser.getControl('Save').click()>>> 'Changes saved' in browser.contentsTrueDone! 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************"", AuthorDownload********