pretaweb.agls

.. image:: https://travis-ci.org/pretaweb/pretaweb.agls.png?branch=master :target: http://travis-ci.org/pretaweb/pretaweb.agls

============= Pretaweb AGLS

.. contents::

Introduction

This package introduces AGLS Metadata into Plone pages.

Compatibility

Tested on plone 4.

Works for the next Plone content type frameworks:

• Archetypes

• Dexterity

Useful Links

• AGLS Standard_
• AGLS Usage Guide_

.. _AGLS Standard: http://www.agls.gov.au/ .. _AGLS Usage Guide: http://www.agls.gov.au/pdf/AGLS%20Metadata%20Standard%20Part%202%20Usage%20Guide.PDF

Changelog

1.0.5 (25-April-2015)

• Fix the documentation display nicely in pypi. [ivanteoh]

1.0.4 (24-April-2015)

• Add default value for title, description, type and format as if Dublin Core metadata is turned on. [ivanteoh]

1.0.3 (09-October-2014)

• Fix the agls index zero error. [ivanteoh]

1.0.2 (10-July-2014)

• DX directives now working. disabling for now. [djay]

1.0.1 (30-May-2014)

• fixed incorrect merge. [djay]

• put in place travis testing. [djay]

1.0 (30-May-2014)

• initial public release. [djay]

1.0alpha1 (29-April-2014)

• handle if schema isn't found. don't error. [djay]

• Add uninstall step for browserlayer. [ivanteoh]

• Fix the Schema could not find 'agls_type'. [Vitaliy Podoba]

• Created recipe with ZopeSkel. [Vitaliy Podoba]

Documentation

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 --

Thanks

Thanks to the following people for support, code, patches, etc:

• Adam Terry
• Dylan Jay
• Ivan Teoh
• Vitaliy Podoba, [e-mail]