Initial import of test files.

"Overwriting" plone.act/plone.txt initially so I can work out how to best
use a layer within the product being tested, in this case plone.app.toolbar.

To run test try

$ python bootstrap
$ ./bin/buildout -c pybot.cfg
$ ./bin/pybot src/plone.app.toolbar/acceptance-tests/
The plone.app.toolbar layer TOOLBAR_FUNCTIONAL_TESTING didn't contain a
full test framework with zserver so when the layer was started no working or
"live" website was available.  Added new layer TOOLBAR_ROBOTFRAMEWORK_TESTING
with an addition layer base z2.ZSERVER.  This adds neccesary testing framework
for thru-the-web testing using Robot Framework and Selenium.
Switched over to using plone.act/plone.txt resource file.  The
'Start browser and wake Plone up' keyword accepts the plone.app.toolbar
layer. But the ${PORT} variable is incorrect for the zserver.  This variable
can be overwritten using the command line argument '--variable PORT:55001'.
So the new command for running test is

  $ ./bin/pybot --variable PORT:55001 src/plone.app.toolbar/acceptance-tests/

For more information about variable scope and priority within Robot Framework
see http://robotframework.googlecode.com/hg/doc/userguide/RobotFrameworkUserGuide.html?r=2.7.1#variable-priorities-and-scopes
For 'Suite Setup' I decided to use a slightly modify version of plone.act's
'Start browser and wake Plone up' keyword.  This plone.act keyword does
some strange things at the end starting with

    Wait until keyword succeeds  30s  1s  Log in as site owner
    Log out
    Zodb teardown

First I'm not sure if a ZSERVER_FIXTURE site has a site owner (which reading
from the plone.app.testing and plone.testing doc I would guess yes) or whether
that line has an issue because the 'Log in as site owner' keyword doesn't have
a return value so wait until keyword suceeds will never succeed.  I suspect
the latter. Also I am not sure what the last two lines (Log out,
Zodb teardown) are supposed to do in this context and am assuming they were
left in by accident in the development of the library. So, for now, I am
using my own version of this keyword.

Modify test slightly giving a better test name and created tests to check
for toolbar whether user logged in or not.  Realized I will need to make a
plone.app.toolbar log in keyword because the plone.act expects standard
Plone UI. More consideration should be taken with design of core library
and various UIs.
Toolbar personal-bar css is slightly different then standard Plone UI
personal-bar so temporarily created another keyword 'Toolbar Log in'.
Added zodb teardown to suite shutdown in order to properly breakdown the
test layer.
Add test fixture profile with sample content.
Renamed layer from TOOLBAR_ROBOTFRAMEWORK_TESTING to TOOLBAR_ACCPETANCE_TESTING.
Addedtest fixture profile with sample content for testing.
Added initialization file, __init__.txt, to the test suite directory,
plone.app.toolbar/acceptance-tests/. Moved common suite setup and suite
teardown routines from the test file to the initialization file.  Removed
keywords that were copies of plone.txt keywords with slight tweaks
fixing issues now fixed within plone.txt itself.

Left 'Toolbar Log in' keyword as the toolbar css is different the
out-of-the-box (sunburst) css. This is either a bug or a conscious design
change.
Removed local acceptance-tests/plone.txt. Using plone.act/plone.txt instead.
Added plone.act, robotsuite, robotframework-selenium2libary to plone.app.toolbar's required additional packages for testing.
Removed plone.act from setup.py. plone.act should be there but as it is yet found on PyPI when one tries to include plone.app.toolbar I suspect that it will error out in that plone.act is not found. So for now to include plone.act you need to bring it in seperately from plone.app.toolbar.