Folderish type to store information and media about a work of art
Project description
Code repository: http://svn.somewhere.com/…
Questions and comments to somemailing_list
Report bugs at http://bug.somewhere.com/..
Change history
Changelog
0.1 (xxxx-xx-xx)
Created recipe with ZopeSkel [David Jonas]
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 Work content type ===============================
In this section we are tesing the Work content type by performing basic operations like adding, updadating and deleting Work content items.
Adding a new Work 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 ‘Work’ and click the ‘Add’ button to get to the add form.
>>> browser.getControl('Work').click()
>>> browser.getControl(name='form.button.Add').click()
>>> 'Work' in browser.contents
True
Now we fill the form and submit it.
>>> browser.getControl(name='title').value = 'Work Sample'
>>> browser.getControl('Save').click()
>>> 'Changes saved' in browser.contents
True
And we are done! We added a new ‘Work’ content item to the portal.
Updating an existing Work 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 Work Sample'
>>> browser.getControl('Save').click()
We check that the changes were applied.
>>> 'Changes saved' in browser.contents True >>> 'New Work Sample' in browser.contents True
Removing a/an Work content item
If we go to the home page, we can see a tab with the ‘New Work Sample’ title in the global navigation tabs.
>>> browser.open(portal_url) >>> 'New Work Sample' in browser.contents True
Now we are going to delete the ‘New Work Sample’ object. First we go to the contents tab and select the ‘New Work Sample’ for deletion.
>>> browser.getLink('Contents').click()
>>> browser.getControl('New Work 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 Work Sample’ tab.
>>> browser.open(portal_url) >>> 'New Work Sample' in browser.contents False
Adding a new Work content item as contributor
Not only site managers are allowed to add Work 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 ‘Work’ and click the ‘Add’ button to get to the add form.
>>> browser.getControl('Work').click()
>>> browser.getControl(name='form.button.Add').click()
>>> 'Work' in browser.contents
True
Now we fill the form and submit it.
>>> browser.getControl(name='title').value = 'Work Sample'
>>> browser.getControl('Save').click()
>>> 'Changes saved' in browser.contents
True
Done! We added a new Work 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
David Jonas, Author
Download
Release history Release notifications | RSS feed
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
