Index: /eduCommons.buildout/tags/3.2.1-rc1/README.txt =================================================================== --- /eduCommons.buildout/tags/3.2.1-rc1/README.txt (revision 444) +++ /eduCommons.buildout/tags/3.2.1-rc1/README.txt (revision 444) @@ -0,0 +1,327 @@ +======================= +Using a custom buildout +======================= + +Note: If you are using Windows, if you do not have PIL installed, or you are +not using Python 2.4 as your main system Python, please see the relevant +sections below. + +You probably got here by running something like: + + $ paster create -t plone3_buildout + +Now, you need to run: + + $ python bootstrap.py + +This will install zc.buildout for you. + +To create an instance immediately, run: + + $ bin/buildout + +This will download Plone's eggs and products for you, as well as other +dependencies, create a new Zope 2 installation (unless you specified +an existing one when you ran "paster create"), and create a new Zope instance +configured with these products. + +You can start your Zope instance by running: + + $ bin/instance start + +or, to run in foreground mode: + + $ bin/instance fg + +To run unit tests, you can use: + + $ bin/instance test -s my.package + +Installing PIL +-------------- + +To use Plone, you need PIL, the Python Imaging Library. If you don't already +have this, download and install it from http://www.pythonware.com/products/pil. + +Using a different Python installation +-------------------------------------- + +Buildout will use your system Python installation by default. However, Zope +2.10 (and by extension, Plone) will only work with Python 2.4. You can verify +which version of Python you have, by running: + + $ python -V + +If that is not a 2.4 version, you need to install Python 2.4 from +http://python.org. If you wish to keep another version as your main system +Python, edit buildout.cfg and add an 'executable' option to the "[buildout]" +section, pointing to a python interpreter binary: + + [buildout] + ... + executable = /path/to/python + +Working with buildout.cfg +------------------------- + +You can change any option in buildout.cfg and re-run bin/buildout to reflect +the changes. This may delete things inside the 'parts' directory, but should +keep your Data.fs and source files intact. + +To save time, you can run buildout in "offline" (-o) and non-updating (-N) +mode, which will prevent it from downloading things and checking for new +versions online: + + $ bin/buildout -Nov + +Creating new eggs +----------------- + +New packages you are working on (but which are not yet released as eggs and +uploaded to the Python Package Index, aka PYPI) should be placed in src. You can do: + + $ cd src/ + $ paster create -t plone my.package + +Use "paster create --list-templates" to see all available templates. Answer +the questions and you will get a new egg. Then tell buildout about your egg +by editing buildout.cfg and adding your source directory to 'develop': + + [buildout] + ... + develop = + src/my.package + +You can list multiple packages here, separated by whitespace or indented +newlines. + +You probably also want the Zope instance to know about the package. Add its +package name to the list of eggs in the "[instance]" section, or under the +main "[buildout]" section: + + [instance] + ... + eggs = + ${buildout:eggs} + ${plone:eggs} + my.package + +Leave the ${buildout:eggs} part in place - it tells the instance to use the +eggs that buildout will have downloaded from the Python Package Index +previously. + +If you also require a ZCML slug for your package, buildout can create one +automatically. Just add the package to the 'zcml' option: + + [instance] + ... + zcml = + my.package + +When you are finished, re-run buildout. Offline, non-updating mode should +suffice: + + $ bin/buildout -Nov + +Developing old-style products +----------------------------- + +If you are developing old-style Zope 2 products (not eggs) then you can do so +by placing the product code in the top-level 'products' directory. This is +analogous to the 'Products/' directory inside a normal Zope 2 instance and is +scanned on start-up for new products. + +Depending on a new egg +---------------------- + +If you want to use a new egg that is in the Python Package Index, all you need +to do is to add it to the "eggs" option under the main "[buildout]" section: + + [buildout] + ... + eggs = + my.package + +If it's listed somewhere else than the Python Package Index, you can add a link +telling buildout where to find it in the 'find-links' option: + + [buildout] + ... + find-links = + http://dist.plone.org + http://download.zope.org/distribution/ + http://effbot.org/downloads + http://some.host.com/packages + +Using existing old-style products +--------------------------------- + +If you are using an old-style (non-egg) product, you can either add it as an +automatically downloaded archive or put it in the top-level "products" folder. +The former is probably better, because it means you can redistribute your +buildout.cfg more easily: + + [productdistros] + recipe = plone.recipe.distros + urls = + http://plone.org/products/someproduct/releases/1.3/someproduct-1.3.tar.gz + +If someproduct-1.3.tar.gz extracts into several products inside a top-level +directory, e.g. SomeProduct-1.3/PartOne and SomeProduct-1.3/PartTwo, then +add it as a "nested package": + + [productdistros] + recipe = plone.recipe.distros + urls = + http://plone.org/products/someproduct/releases/1.3/someproduct-1.3.tar.gz + nested-packages = + someproduct-1.3.tar.gz + +Alternatively, if it extracts to a directory which contains the version +number, add it as a "version suffix package": + + [productdistros] + recipe = plone.recipe.distros + urls = + http://plone.org/products/someproduct/releases/1.3/someproduct-1.3.tar.gz + version-suffix-packages = + someproduct-1.3.tar.gz + +You can also track products by adding a new bundle checkout part. It +doesn't strictly have to be an svn bundle at all, any svn location will do, +and cvs is also supported: + + [buildout] + ... + parts = + plone + zope2 + productdistros + myproduct + instance + zopepy + +Note that "myproduct" comes before the "instance" part. You then +need to add a new section to buildout.cfg: + + [myproduct] + recipe = plone.recipe.bundlecheckout + url = http://svn.plone.org/svn/collective/myproduct/trunk + +Finally, you need to tell Zope to find this new checkout and add it to its +list of directories that are scanned for products: + + [instance] + ... + products = + ${buildout:directory}/products + ${productdistros:location} + ${plonebundle:location} + ${myproduct:location} + +Without this last step, the "myproduct" part is simply managing an svn +checkout and could potentially be used for something else instead. + +============= +Using Windows +============= + +To use buildout on Windows, you will need to install a few dependencies which +other platforms manage on their own. + +Here are the steps you need to follow (thanks to Hanno Schlichting for these): + +Python (http://python.org) +-------------------------- + + - Download and install Python 2.4.4 using the Windows installer from + http://www.python.org/ftp/python/2.4.4/python-2.4.4.msi + Select 'Install for all users' and it will put Python into the + "C:\Python24" folder by default. + + - You also want the pywin32 extensions available from + http://downloads.sourceforge.net/pywin32/pywin32-210.win32-py2.4.exe?modtime=1159009237&big_mirror=0 + + - And as a last step you want to download the Python imaging library available + from http://effbot.org/downloads/PIL-1.1.6.win32-py2.4.exe + + - If you develop Zope based applications you will usually only need Python 2.4 + at the moment, so it's easiest to put the Python binary on the systems PATH, + so you don't need to specify its location manually each time you call it. + + Thus, put "C:\Python24" and "C:\Python24\Scripts" onto the PATH. You can + find the PATH definition in the control panel under system preferences on + the advanced tab at the bottom. The button is called environment variables. + You want to add it at the end of the already existing PATH in the system + section. Paths are separated by a semicolons. + + - You can test if this was successful by opening a new shell (cmd) and type + in 'python -V'. It should report version 2.4.4 (or whichever version you + installed). + + Opening a new shell can be done quickly by using the key combination + 'Windows-r' or if you are using Parallels on a Mac 'Apple-r'. Type in 'cmd' + into the popup box that opens up and hit enter. + + +Subversion (http://subversion.tigris.org) +----------------------------------------- + + - Download the nice installer from + http://subversion.tigris.org/files/documents/15/35379/svn-1.4.2-setup.exe + + - Run the installer. It defaults to installing into + "C:\Program Files\Subversion". + + - Now put the install locations bin subfolder (for example + "C:\Program Files\Subversion\bin") on your system PATH in the same way you + put Python on it. + + - Open a new shell again and type in: 'svn --version' it should report + version 1.4.2 or newer. + + +MinGW (http://www.mingw.org/) +----------------------------- + + This is a native port of the gcc compiler and its dependencies for Windows. + There are other approaches enabling you to compile Python C extensions on + Windows including Cygwin and using the official Microsoft C compiler, but this + is a lightweight approach that uses only freely available tools. As + it's used by a lot of people chances are high it will work for you and there's + plenty of documentation out there to help you in troubleshooting problems. + + - Download the MinGW installer from + http://downloads.sourceforge.net/mingw/MinGW-5.1.3.exe?modtime=1168794334&big_mirror=1 + + - The installer will ask you which options you would like to install. Choose + base and make here. It will install into "C:\MinGW" by default. The install + might take some time as it's getting files from sourceforge.net and you + might need to hit 'retry' a couple of times. + + - Now put the install location's bin subfolder (for example "C:\MinGW\bin") on + your system PATH in the same way you put Python on it. + + - Test this again by typing in: 'gcc --version' on a newly opened shell and + it should report version 3.4.2 or newer. + + +Configure Distutils to use MinGW +-------------------------------- + + Some general information are available from + http://www.mingw.org/MinGWiki/index.php/Python%20extensions for example but + you don't need to read them all. + + - Create a file called 'distutils.cfg' in "C:\Python24\Lib\distutils". Open it + with a text editor ('notepad distutils.cfg') and fill in the following lines: + + [build] + compiler=mingw32 + + This will tell distutils to use MinGW as the default compiler, so you don't + need to specify it manually using "--compiler=mingw32" while calling a + package's setup.py with a command that involves building C extensions. This + is extremely useful if the build command is written down in a buildout + recipe where you cannot change the options without hacking the recipe + itself. The z2c.recipe.zope2install used in ploneout is one such example. Index: /eduCommons.buildout/tags/3.2.1-rc1/bootstrap.py =================================================================== --- /eduCommons.buildout/tags/3.2.1-rc1/bootstrap.py (revision 444) +++ /eduCommons.buildout/tags/3.2.1-rc1/bootstrap.py (revision 444) @@ -0,0 +1,55 @@ +############################################################################## +# +# Copyright (c) 2006 Zope Corporation and Contributors. +# All Rights Reserved. +# +# This software is subject to the provisions of the Zope Public License, +# Version 2.1 (ZPL). A copy of the ZPL should accompany this distribution. +# THIS SOFTWARE IS PROVIDED "AS IS" AND ANY AND ALL EXPRESS OR IMPLIED +# WARRANTIES ARE DISCLAIMED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED +# WARRANTIES OF TITLE, MERCHANTABILITY, AGAINST INFRINGEMENT, AND FITNESS +# FOR A PARTICULAR PURPOSE. +# +############################################################################## +"""Bootstrap a buildout-based project + +Simply run this script in a directory containing a buildout.cfg. +The script accepts buildout command-line options, so you can +use the -c option to specify an alternate configuration file. + +$Id$ +""" + +import os, shutil, sys, tempfile, urllib2 + +tmpeggs = tempfile.mkdtemp() + +try: + import pkg_resources +except ImportError: + ez = {} + exec urllib2.urlopen('http://peak.telecommunity.com/dist/ez_setup.py' + ).read() in ez + ez['use_setuptools'](to_dir=tmpeggs, download_delay=0) + + import pkg_resources + +cmd = 'from setuptools.command.easy_install import main; main()' +if sys.platform == 'win32': + cmd = '"%s"' % cmd # work around spawn lamosity on windows + +ws = pkg_resources.working_set +assert os.spawnle( + os.P_WAIT, sys.executable, sys.executable, + '-c', cmd, '-mqNxd', tmpeggs, 'zc.buildout', + dict(os.environ, + PYTHONPATH= + ws.find(pkg_resources.Requirement.parse('setuptools')).location + ), + ) == 0 + +ws.add_entry(tmpeggs) +ws.require('zc.buildout') +import zc.buildout.buildout +zc.buildout.buildout.main(sys.argv[1:] + ['bootstrap']) +shutil.rmtree(tmpeggs) Index: /eduCommons.buildout/tags/3.2.1-rc1/buildout.cfg =================================================================== --- /eduCommons.buildout/tags/3.2.1-rc1/buildout.cfg (revision 444) +++ /eduCommons.buildout/tags/3.2.1-rc1/buildout.cfg (revision 444) @@ -0,0 +1,180 @@ +[buildout] +parts = + zope2 + productdistros + instance + fss + zopepy + test + test-coverage + coverage-report + +# Add additional egg download sources here. dist.plone.org contains archives +# of Plone packages. +find-links = + http://dist.plone.org/thirdparty + http://dist.plone.org + http://download.zope.org/ppix/ + http://download.zope.org/distribution/ + http://effbot.org/downloads + ftp://xmlsoft.org/libxml2/python/libxml2-python-2.6.15.tar.gz + http://ufpr.dl.sourceforge.net/sourceforge/pyxml/PyXML-0.8.4.tar.gz + http://pypi.python.org/packages/source/p/plone.reload/plone.reload-0.10.tar.gz + +extends = http://dist.plone.org/release/3.2.1/versions.cfg +versions = versions + +# Add additional eggs here +# elementtree is required by Plone +eggs = + Plone + PIL + elementtree + libxml2-python + PyXML + BeautifulSoup + infrae.subversion + collective.captcha + collective.plonebookmarklets + collective.contentlicensing + collective.imstransport + collective.jaop + collective.oaiintercom + collective.searchandreplace + collective.zipfiletransport + enpraxis.leftskin + enpraxis.staticsite + enpraxis.educommons + enpraxis.wordpressexchange + plone.reload + iw.fss + plone.mocktestcase + Products.CacheSetup + +# Reference any eggs you are developing here, one per line +# e.g.: develop = src/my.package +develop = + src/collective.plonebookmarklets + src/collective.contentlicensing + src/collective.imstransport + src/collective.jaop + src/collective.oaiintercom + src/collective.searchandreplace + src/collective.zipfiletransport + src/enpraxis.leftskin + src/enpraxis.staticsite + src/enpraxis.educommons + src/enpraxis.wordpressexchange + +[versions] +zope.component = 3.5.1 + +[zope2] +recipe = plone.recipe.zope2install +url = ${versions:zope2-url} +fake-zope-eggs = true +skip-fake-eggs = + ZConfig + ZODB3 + pytz + zope.testing + zope.component + zope.i18n + +# Use this section to download additional old-style products. +# List any number of URLs for product tarballs under URLs (separate +# with whitespace, or break over several lines, with subsequent lines +# indented). If any archives contain several products inside a top-level +# directory, list the archive file name (i.e. the last part of the URL, +# normally with a .tar.gz suffix or similar) under 'nested-packages'. +# If any archives extract to a product directory with a version suffix, list +# the archive name under 'version-suffix-packages'. +[productdistros] +recipe = plone.recipe.distros +urls = + http://www.infrae.com/download/ProxyIndex/1.2.1/ProxyIndex-1.2.1.tgz + http://plone.org/products/linguaplone/releases/2.1.1/LinguaPlone-2.1.1.tar.gz +nested-packages = +version-suffix-packages = + +[instance] +recipe = plone.recipe.zope2instance +zope2-location = ${zope2:location} +user = admin:test1234 +http-address = 8080 +debug-mode = on +verbose-security = on +zcml = + plone.mocktestcase + +# If you want Zope to know about any additional eggs, list them here. +# This should include any development eggs you listed in develop-eggs above, +# e.g. eggs = ${buildout:eggs} ${plone:eggs} my.package +eggs = + ${buildout:eggs} + +# If you want to register ZCML slugs for any packages, list them here. +# e.g. zcml = my.package my.other.package +zcml = + collective.plonebookmarklets + collective.contentlicensing + collective.imstransport + collective.jaop + collective.oaiintercom + collective.searchandreplace + collective.zipfiletransport + enpraxis.leftskin + enpraxis.leftskin-overrides + enpraxis.staticsite + enpraxis.educommons + enpraxis.educommons-overrides + enpraxis.wordpressexchange + iw.fss + plone.reload + + + +products = + ${buildout:directory}/products + ${productdistros:location} + +[zopepy] +recipe = zc.recipe.egg +eggs = ${instance:eggs} +interpreter = zopepy +extra-paths = ${zope2:location}/lib/python +scripts = zopepy + +[test] +recipe = collective.recipe.z2testrunner +defaults = --ndiff -v +zope2part = instance +packages = collective.plonebookmarklets + collective.searchandreplace + collective.imstransport + collective.zipfiletransport + collective.jaop + collective.oaiintercom + enpraxis.educommons + enpraxis.leftskin + enpraxis.staticsite + +[test-coverage] +recipe = collective.recipe.z2testrunner +packages = ${test:packages} +zope2part = instance +defaults = --ndiff -v --coverage=${buildout:directory}/coverage + +[coverage-report] +recipe = zc.recipe.egg +eggs = z3c.coverage +scripts = coverage=coverage-report +arguments = ('${buildout:directory}/coverage', '${buildout:directory}/coverage/report') + +[fss] +recipe = iw.recipe.fss +zope-instances = + ${instance:location} +storages = +# The first is always generic + global / Index: /eduCommons.buildout/tags/3.2.1-rc1/deployment.cfg =================================================================== --- /eduCommons.buildout/tags/3.2.1-rc1/deployment.cfg (revision 444) +++ /eduCommons.buildout/tags/3.2.1-rc1/deployment.cfg (revision 444) @@ -0,0 +1,72 @@ +[buildout] +extends = + buildout.cfg + +parts = + plone + zope2 + productdistros + instance + fss + zopepy + test + test-coverage + coverage-report + zeoserver + plonesite + +find-links += + http://localhost/files/ + +# Do not load any development eggs +develop = + + +[zeoserver] +recipe = plone.recipe.zope2zeoserver +zope2-location = ${instance:zope2-location} +zeo-address = ${instance:zeo-address} + +[instance] +recipe = plone.recipe.zope2instance +zope2-location = ${zope2:location} +user = admin:test1234 +http-address = 8080 +effective-user = educommons +zeo-client = true +zeo-address = 8100 +zodb-cache-size = 1500 +zeo-client-cache-size = 300MB +debug-mode = off +verbose-security = off +eggs += Products.CacheSetup +environment-vars = + PYTHON_EGG_CACHE ${buildout:directory}/var/.python-eggs + +[plonesite] +recipe = collective.recipe.plonesite +site-id = eduCommons +instance = instance +zeoserver = zeoserver +profiles = + collective.contentlicensing:default + collective.imstransport:default + collective.plonebookmarklets:default + collective.zipfiletransport:default + collective.searchandreplace:default + enpraxis.leftskin:default + enpraxis.educommons:default + iw.fss:default + Products.LinguaPlone:LinguaPlone + Products.CacheSetup:default + Products.CMFPlacefulWorkflow:CMFPlacefulWorkflow + plone.app.iterate:plone.app.iterate + +[fss] +recipe = iw.recipe.fss +zope-instances = + ${instance:location} +storages = + global / directory ${buildout:directory}/var/fss_storage ${buildout:directory}/var/fss_backup + + Index: /eduCommons.buildout/tags/3.2.1-rc1/products/README.txt =================================================================== --- /eduCommons.buildout/tags/3.2.1-rc1/products/README.txt (revision 444) +++ /eduCommons.buildout/tags/3.2.1-rc1/products/README.txt (revision 444) @@ -0,0 +1,1 @@ +Old-style Zope products you are developing can be added here Index: /eduCommons.buildout/tags/3.2.1-rc1/src/EXTERNALS.txt =================================================================== --- /eduCommons.buildout/tags/3.2.1-rc1/src/EXTERNALS.txt (revision 444) +++ /eduCommons.buildout/tags/3.2.1-rc1/src/EXTERNALS.txt (revision 444) @@ -0,0 +1,13 @@ +# svn propset svn:externals -F EXTERNALS.txt . +# eduCommons eggs +collective.plonebookmarklets https://svn.plone.org/svn/collective/collective.plonebookmarklets/trunk +collective.contentlicensing https://svn.plone.org/svn/collective/collective.contentlicensing/trunk +collective.imstransport https://svn.plone.org/svn/collective.imstransport/trunk +collective.jaop https://svn.plone.org/svn/collective/collective.jaop/trunk +collective.oaiintercom https://svn.plone.org/svn/collective/collective.oaiintercom/trunk +collective.searchandreplace https://svn.plone.org/svn/collective/collective.searchandreplace/trunk +collective.zipfiletransport https://svn.plone.org/svn/collective/collective.zipfiletransport/trunk +enpraxis.leftskin https://enpraxis.net/svn/eduCommons32/enpraxis.leftskin/trunk +enpraxis.educommons https://enpraxis.net/svn/eduCommons32/enpraxis.educommons/trunk +enpraxis.staticsite https://enpraxis.net/svn/eduCommons32/enpraxis.staticsite/trunk +enpraxis.wordpressexchange https://enpraxis.net/svn/eduCommons32/enpraxis.wordpressexchange/trunk Index: /eduCommons.buildout/tags/3.2.1-rc1/src/rcom.recipe.seleniumenv/CHANGES.txt =================================================================== --- /eduCommons.buildout/tags/3.2.1-rc1/src/rcom.recipe.seleniumenv/CHANGES.txt (revision 444) +++ /eduCommons.buildout/tags/3.2.1-rc1/src/rcom.recipe.seleniumenv/CHANGES.txt (revision 444) @@ -0,0 +1,7 @@ +0.1 (2009-01-05) +================== + - Created recipe with ZopeSkel [Santiago Suarez Ordonez]. + +1.0 (2009-02-14) +================== + - Ended code changes and uploaded the egg to pypi [Santiago Suarez Ordonez]. Index: /eduCommons.buildout/tags/3.2.1-rc1/src/rcom.recipe.seleniumenv/CONTRIBUTORS.txt =================================================================== --- /eduCommons.buildout/tags/3.2.1-rc1/src/rcom.recipe.seleniumenv/CONTRIBUTORS.txt (revision 444) +++ /eduCommons.buildout/tags/3.2.1-rc1/src/rcom.recipe.seleniumenv/CONTRIBUTORS.txt (revision 444) @@ -0,0 +1,2 @@ +Santiago Suarez Ordonez, Author +Juan Pablo Gimenez, Contributor Index: /eduCommons.buildout/tags/3.2.1-rc1/src/rcom.recipe.seleniumenv/README.txt =================================================================== --- /eduCommons.buildout/tags/3.2.1-rc1/src/rcom.recipe.seleniumenv/README.txt (revision 444) +++ /eduCommons.buildout/tags/3.2.1-rc1/src/rcom.recipe.seleniumenv/README.txt (revision 444) @@ -0,0 +1,7 @@ +.. contents:: + + +- Code repository: http://svn.rcom.com.ar/rcom.recipe.seleniumenv +- Questions and comments to santiycr atrcom dotcom dotar +- Report bugs at santiycr atrcom dotcom dotar + Index: /eduCommons.buildout/tags/3.2.1-rc1/src/rcom.recipe.seleniumenv/bootstrap.py =================================================================== --- /eduCommons.buildout/tags/3.2.1-rc1/src/rcom.recipe.seleniumenv/bootstrap.py (revision 444) +++ /eduCommons.buildout/tags/3.2.1-rc1/src/rcom.recipe.seleniumenv/bootstrap.py (revision 444) @@ -0,0 +1,52 @@ +############################################################################## +# +# Copyright (c) 2006 Zope Corporation and Contributors. +# All Rights Reserved. +# +# This software is subject to the provisions of the Zope Public License, +# Version 2.1 (ZPL). A copy of the ZPL should accompany this distribution. +# THIS SOFTWARE IS PROVIDED "AS IS" AND ANY AND ALL EXPRESS OR IMPLIED +# WARRANTIES ARE DISCLAIMED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED +# WARRANTIES OF TITLE, MERCHANTABILITY, AGAINST INFRINGEMENT, AND FITNESS +# FOR A PARTICULAR PURPOSE. +# +############################################################################## +"""Bootstrap a buildout-based project + +Simply run this script in a directory containing a buildout.cfg. +The script accepts buildout command-line options, so you can +use the -c option to specify an alternate configuration file. + +$Id$ +""" + +import os, shutil, sys, tempfile, urllib2 + +tmpeggs = tempfile.mkdtemp() + +ez = {} +exec urllib2.urlopen('http://peak.telecommunity.com/dist/ez_setup.py' + ).read() in ez +ez['use_setuptools'](to_dir=tmpeggs, download_delay=0) + +import pkg_resources + +cmd = 'from setuptools.command.easy_install import main; main()' +if sys.platform == 'win32': + cmd = '"%s"' % cmd # work around spawn lamosity on windows + +ws = pkg_resources.working_set +assert os.spawnle( + os.P_WAIT, sys.executable, sys.executable, + '-c', cmd, '-mqNxd', tmpeggs, 'zc.buildout', + dict(os.environ, + PYTHONPATH= + ws.find(pkg_resources.Requirement.parse('setuptools')).location + ), + ) == 0 + +ws.add_entry(tmpeggs) +ws.require('zc.buildout') +import zc.buildout.buildout +zc.buildout.buildout.main(sys.argv[1:] + ['bootstrap']) +shutil.rmtree(tmpeggs) Index: /eduCommons.buildout/tags/3.2.1-rc1/src/rcom.recipe.seleniumenv/buildout.cfg =================================================================== --- /eduCommons.buildout/tags/3.2.1-rc1/src/rcom.recipe.seleniumenv/buildout.cfg (revision 444) +++ /eduCommons.buildout/tags/3.2.1-rc1/src/rcom.recipe.seleniumenv/buildout.cfg (revision 444) @@ -0,0 +1,7 @@ +[buildout] +develop = . +parts = test + +[test] +recipe = zc.recipe.testrunner +eggs = rcom.recipe.seleniumenv [tests] Index: /eduCommons.buildout/tags/3.2.1-rc1/src/rcom.recipe.seleniumenv/rcom.recipe.seleniumenv.egg-info/PKG-INFO =================================================================== --- /eduCommons.buildout/tags/3.2.1-rc1/src/rcom.recipe.seleniumenv/rcom.recipe.seleniumenv.egg-info/PKG-INFO (revision 444) +++ /eduCommons.buildout/tags/3.2.1-rc1/src/rcom.recipe.seleniumenv/rcom.recipe.seleniumenv.egg-info/PKG-INFO (revision 444) @@ -0,0 +1,192 @@ +Metadata-Version: 1.0 +Name: rcom.recipe.seleniumenv +Version: 1.0dev-r316 +Summary: A recipe for setting a ready-to-use selenium RC environment +Home-page: www.rcom.com.ar +Author: Santiago Suarez Ordonez +Author-email: santiycr@rcom.com.ar +License: ZPL +Description: .. contents:: + + + - Code repository: http://svn.rcom.com.ar/rcom.recipe.seleniumenv + - Questions and comments to santiycr atrcom dotcom dotar + - Report bugs at santiycr atrcom dotcom dotar + + + Detailed Documentation + ********************** + + Supported options + ================= + + The recipe supports the following options: + + seleniumversion + The version of selenium to use, the version numbers can be taken from + http://release.seleniumhq.org/selenium-remote-control/. Default: nightlyBuild. + + eggs + The eggs to include in the runner path. Any product included in the path will be + accesible for the runner to search and run selenium tests from. + + java-cmd + The commando used to run the selenium server. Default: java. + + Example usage + ============= + + The basic buildout that uses the recipe should look like the following:: + + >>> write('buildout.cfg', + ... """ + ... [buildout] + ... parts = seleniumenv + ... + ... [seleniumenv] + ... recipe = rcom.recipe.seleniumenv + ... seleniumversion = 1.0-beta-2 + ... eggs = ${instance:eggs} + + + The seleniumrunner script + ========================= + + The selenium runner is a scipt to find and run **selenium tests**, it will + be on your bin directory once the recipe is instanlled + It receives different parameters and it's main objective is to simplify the + tests execution and reporting procedure. + This script will wake-up the selenium RC server, search and run the tests + and then shutdown the server and report the tests result. + Once the recipe has been installed, a tests runner should be placed on the bin directory + + Running the tests + ----------------- + + To run the suite of tests buldled with any product, the first thing to do after + the buildout has been run is to prepare a Plone site to test (if the user doesn't + have a Plone site to test, yet). + For this to be done, you must first wake up the instance:: + + ./bin/instance start + + To run all the selenium tests for a product the user should pass at least two + parameters: + + -i instance + The Plone site's name. + + -s product + The product in which the runner will search for tests to run. + + An example test execution will be:: + + $ ./bin/seleniumrunner -i testPloneSite -s namespace.product + + This will search all the **selenium** tests for the product and run them + on http://localhost:/testPloneSite. + + For running a particular test, the -t parameter should be passed to the runner:: + + $ ./bin/seleniumrunner -i testPloneSite -s namespace.product -t exampleTest + + .. Note:: + + Please notice that the exampleTest.py test should be stored in the + respective location and added to the __init__py file (See `Creating a test`_) + + Creating a test + --------------- + + The seleniumrunner script will look for all the classes that inherit from + unittest.TestCase on a specified package or module located under this kind of + path:: + + namespace.product/namespace/product/tests/seleniumtests + + Tests development guidelines + ++++++++++++++++++++++++++++ + + To create a test, there are certain basic rules to follow: + + #) The test should inherit from unittest.TestCase class (this can be done + indirectly also). + #) The test should use certain global variables for the code to work + on different environments and Plone instances. These are: + + - browser: For the browser used for the tests + + - port: For the port used to communicate with the server + + - url: For the url of the application under test + + - instance: The Plone site name (this depends on + the name used for the site's creation). + + This variables should never be changed inside the test code, as the + seleniumrunner script will set them at runtime according with the parameters + received. + + All this rules can be seen applied to the following `Example test`_. + + Example test + ++++++++++++ + + The following is an example test, it can be used as the basic + structure for future tests:: + + from selenium import selenium + import unittest + + class NewTest(unittest.TestCase): + def setUp(self): + self.verificationErrors = [] + self.selenium = selenium("localhost", port, browser, url) + self.selenium.start() + + def test_new(self): + sel = self.selenium + sel.open(instance + "/login.html") + # Do specific tests in here + + def tearDown(self): + self.selenium.stop() + self.assertEqual([], self.verificationErrors) + + Notice that the test doesn't have much changes from the basic test exported using + `Selenium IDE `_, the firefox extension. The + only difference are the variables used for the instanciation inside the *setUp* method. + + .. Note:: + + Please notice that the "instance" variable will have to be used in + each *open* command for the users to provide the correct location + of the eduCommons plone site to test. + + Contributors + ************ + + Santiago Suarez Ordonez, Author + Juan Pablo Gimenez, Contributor + + Change history + ************** + + 0.1 (2009-01-05) + ================== + - Created recipe with ZopeSkel [Santiago Suarez Ordonez]. + + 1.0 (2009-02-14) + ================== + - Ended code changes and uploaded the egg to pypi [Santiago Suarez Ordonez]. + + Download + ******** + +Keywords: selenium rc testing plone ajax recipe +Platform: UNKNOWN +Classifier: Framework :: Buildout +Classifier: Intended Audience :: Developers +Classifier: Topic :: Software Development :: Build Tools +Classifier: Topic :: Software Development :: Libraries :: Python Modules +Classifier: License :: OSI Approved :: Zope Public License Index: /eduCommons.buildout/tags/3.2.1-rc1/src/rcom.recipe.seleniumenv/rcom.recipe.seleniumenv.egg-info/SOURCES.txt =================================================================== --- /eduCommons.buildout/tags/3.2.1-rc1/src/rcom.recipe.seleniumenv/rcom.recipe.seleniumenv.egg-info/SOURCES.txt (revision 444) +++ /eduCommons.buildout/tags/3.2.1-rc1/src/rcom.recipe.seleniumenv/rcom.recipe.seleniumenv.egg-info/SOURCES.txt (revision 444) @@ -0,0 +1,24 @@ +CHANGES.txt +CONTRIBUTORS.txt +README.txt +bootstrap.py +buildout.cfg +setup.cfg +setup.py +rcom/__init__.py +rcom.recipe.seleniumenv.egg-info/PKG-INFO +rcom.recipe.seleniumenv.egg-info/SOURCES.txt +rcom.recipe.seleniumenv.egg-info/dependency_links.txt +rcom.recipe.seleniumenv.egg-info/entry_points.txt +rcom.recipe.seleniumenv.egg-info/namespace_packages.txt +rcom.recipe.seleniumenv.egg-info/not-zip-safe +rcom.recipe.seleniumenv.egg-info/requires.txt +rcom.recipe.seleniumenv.egg-info/top_level.txt +rcom/recipe/__init__.py +rcom/recipe/seleniumenv/HTMLTestRunner.py +rcom/recipe/seleniumenv/README.txt +rcom/recipe/seleniumenv/__init__.py +rcom/recipe/seleniumenv/defaults.cfg +rcom/recipe/seleniumenv/seleniumRunnerBase.py +rcom/recipe/seleniumenv/tests/__init__.py +rcom/recipe/seleniumenv/tests/test_docs.py Index: /eduCommons.buildout/tags/3.2.1-rc1/src/rcom.recipe.seleniumenv/rcom.recipe.seleniumenv.egg-info/dependency_links.txt =================================================================== --- /eduCommons.buildout/tags/3.2.1-rc1/src/rcom.recipe.seleniumenv/rcom.recipe.seleniumenv.egg-info/dependency_links.txt (revision 444) +++ /eduCommons.buildout/tags/3.2.1-rc1/src/rcom.recipe.seleniumenv/rcom.recipe.seleniumenv.egg-info/dependency_links.txt (revision 444) @@ -0,0 +1,1 @@ + Index: /eduCommons.buildout/tags/3.2.1-rc1/src/rcom.recipe.seleniumenv/rcom.recipe.seleniumenv.egg-info/entry_points.txt =================================================================== --- /eduCommons.buildout/tags/3.2.1-rc1/src/rcom.recipe.seleniumenv/rcom.recipe.seleniumenv.egg-info/entry_points.txt (revision 444) +++ /eduCommons.buildout/tags/3.2.1-rc1/src/rcom.recipe.seleniumenv/rcom.recipe.seleniumenv.egg-info/entry_points.txt (revision 444) @@ -0,0 +1,3 @@ +[zc.buildout] +default = rcom.recipe.seleniumenv:Recipe + Index: /eduCommons.buildout/tags/3.2.1-rc1/src/rcom.recipe.seleniumenv/rcom.recipe.seleniumenv.egg-info/namespace_packages.txt =================================================================== --- /eduCommons.buildout/tags/3.2.1-rc1/src/rcom.recipe.seleniumenv/rcom.recipe.seleniumenv.egg-info/namespace_packages.txt (revision 444) +++ /eduCommons.buildout/tags/3.2.1-rc1/src/rcom.recipe.seleniumenv/rcom.recipe.seleniumenv.egg-info/namespace_packages.txt (revision 444) @@ -0,0 +1,2 @@ +rcom +rcom.recipe Index: /eduCommons.buildout/tags/3.2.1-rc1/src/rcom.recipe.seleniumenv/rcom.recipe.seleniumenv.egg-info/not-zip-safe =================================================================== --- /eduCommons.buildout/tags/3.2.1-rc1/src/rcom.recipe.seleniumenv/rcom.recipe.seleniumenv.egg-info/not-zip-safe (revision 444) +++ /eduCommons.buildout/tags/3.2.1-rc1/src/rcom.recipe.seleniumenv/rcom.recipe.seleniumenv.egg-info/not-zip-safe (revision 444) @@ -0,0 +1,1 @@ + Index: /eduCommons.buildout/tags/3.2.1-rc1/src/rcom.recipe.seleniumenv/rcom.recipe.seleniumenv.egg-info/requires.txt =================================================================== --- /eduCommons.buildout/tags/3.2.1-rc1/src/rcom.recipe.seleniumenv/rcom.recipe.seleniumenv.egg-info/requires.txt (revision 444) +++ /eduCommons.buildout/tags/3.2.1-rc1/src/rcom.recipe.seleniumenv/rcom.recipe.seleniumenv.egg-info/requires.txt (revision 444) @@ -0,0 +1,8 @@ +setuptools +zc.buildout +hexagonit.recipe.download +zc.recipe.egg + +[tests] +zope.testing +zc.buildout Index: /eduCommons.buildout/tags/3.2.1-rc1/src/rcom.recipe.seleniumenv/rcom.recipe.seleniumenv.egg-info/top_level.txt =================================================================== --- /eduCommons.buildout/tags/3.2.1-rc1/src/rcom.recipe.seleniumenv/rcom.recipe.seleniumenv.egg-info/top_level.txt (revision 444) +++ /eduCommons.buildout/tags/3.2.1-rc1/src/rcom.recipe.seleniumenv/rcom.recipe.seleniumenv.egg-info/top_level.txt (revision 444) @@ -0,0 +1,1 @@ +rcom Index: /eduCommons.buildout/tags/3.2.1-rc1/src/rcom.recipe.seleniumenv/rcom/__init__.py =================================================================== --- /eduCommons.buildout/tags/3.2.1-rc1/src/rcom.recipe.seleniumenv/rcom/__init__.py (revision 444) +++ /eduCommons.buildout/tags/3.2.1-rc1/src/rcom.recipe.seleniumenv/rcom/__init__.py (revision 444) @@ -0,0 +1,6 @@ +# See http://peak.telecommunity.com/DevCenter/setuptools#namespace-packages +try: + __import__('pkg_resources').declare_namespace(__name__) +except ImportError: + from pkgutil import extend_path + __path__ = extend_path(__path__, __name__) Index: /eduCommons.buildout/tags/3.2.1-rc1/src/rcom.recipe.seleniumenv/rcom/recipe/__init__.py =================================================================== --- /eduCommons.buildout/tags/3.2.1-rc1/src/rcom.recipe.seleniumenv/rcom/recipe/__init__.py (revision 444) +++ /eduCommons.buildout/tags/3.2.1-rc1/src/rcom.recipe.seleniumenv/rcom/recipe/__init__.py (revision 444) @@ -0,0 +1,6 @@ +# See http://peak.telecommunity.com/DevCenter/setuptools#namespace-packages +try: + __import__('pkg_resources').declare_namespace(__name__) +except ImportError: + from pkgutil import extend_path + __path__ = extend_path(__path__, __name__) Index: /eduCommons.buildout/tags/3.2.1-rc1/src/rcom.recipe.seleniumenv/rcom/recipe/seleniumenv/HTMLTestRunner.py =================================================================== --- /eduCommons.buildout/tags/3.2.1-rc1/src/rcom.recipe.seleniumenv/rcom/recipe/seleniumenv/HTMLTestRunner.py (revision 444) +++ /eduCommons.buildout/tags/3.2.1-rc1/src/rcom.recipe.seleniumenv/rcom/recipe/seleniumenv/HTMLTestRunner.py (revision 444) @@ -0,0 +1,774 @@ +""" +A TestRunner for use with the Python unit testing framework. It +generates a HTML report to show the result at a glance. + +The simplest way to use this is to invoke its main method. E.g. + + import unittest + import HTMLTestRunner + + ... define your tests ... + + if __name__ == '__main__': + HTMLTestRunner.main() + + +For more customization options, instantiates a HTMLTestRunner object. +HTMLTestRunner is a counterpart to unittest's TextTestRunner. E.g. + + # output to a file + fp = file('my_report.html', 'wb') + runner = HTMLTestRunner.HTMLTestRunner( + stream=fp, + title='My unit test', + description='This demonstrates the report output by HTMLTestRunner.' + ) + + # Use an external stylesheet. + # See the Template_mixin class for more customizable options + runner.STYLESHEET_TMPL = '' + + # run the test + runner.run(my_test_suite) + + +------------------------------------------------------------------------ +Copyright (c) 2004-2006, Wai Yip Tung +All rights reserved. + +Redistribution and use in source and binary forms, with or without +modification, are permitted provided that the following conditions are +met: + +* Redistributions of source code must retain the above copyright notice, + this list of conditions and the following disclaimer. +* Redistributions in binary form must reproduce the above copyright + notice, this list of conditions and the following disclaimer in the + documentation and/or other materials provided with the distribution. +* Neither the name Wai Yip Tung nor the names of its contributors may be + used to endorse or promote products derived from this software without + specific prior written permission. + +THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS +IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED +TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A +PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER +OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, +EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, +PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR +PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF +LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING +NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS +SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. +""" + +# URL: http://tungwaiyip.info/software/HTMLTestRunner.html + +__author__ = "Wai Yip Tung" +__version__ = "0.8.1" + + +""" +Changes in 0.8.1 +* Thank you for Wolfgang Borgert's patch. +* Validated XHTML. +* Added description of test classes and test cases. + +Changes in 0.8.0 +* Define Template_mixin class for customization. +* Workaround a IE 6 bug that it does not treat + +%(heading)s +%(report)s +%(ending)s + + + +""" + # variables: (title, generator, stylesheet, heading, report, ending) + + + # ------------------------------------------------------------------------ + # Stylesheet + # + # alternatively use a for external style sheet, e.g. + # + + STYLESHEET_TMPL = """ + +""" + + + + # ------------------------------------------------------------------------ + # Heading + # + + HEADING_TMPL = """
+

%(title)s

+%(parameters)s +

%(description)s

+
+ +""" # variables: (title, parameters, description) + + HEADING_ATTRIBUTE_TMPL = """

%(name)s: %(value)s

+""" # variables: (name, value) + + + + # ------------------------------------------------------------------------ + # Report + # + + REPORT_TMPL = """ +

Show +Summary +Failed +All +

+ ++++++++ + + + + + + + + +%(test_list)s + + + + + + + + +
Test Group/Test caseCountPassFailErrorView
Total%(count)s%(Pass)s%(fail)s%(error)s 
+""" # variables: (test_list, count, Pass, fail, error) + + REPORT_CLASS_TMPL = r""" + + %(desc)s + %(count)s + %(Pass)s + %(fail)s + %(error)s + Detail + +""" # variables: (style, desc, count, Pass, fail, error, cid) + + + REPORT_TEST_WITH_OUTPUT_TMPL = r""" + +
%(desc)s
+ %(status)s%(script)s + +""" # variables: (tid, Class, style, desc, status) + + + REPORT_TEST_NO_OUTPUT_TMPL = r""" + +
%(desc)s
+ %(status)s + +""" # variables: (tid, Class, style, desc, status) + + + REPORT_TEST_OUTPUT_TMPL = r""" + +""" # variables: (id, output) + + + + # ------------------------------------------------------------------------ + # ENDING + # + + ENDING_TMPL = """
 
""" + +# -------------------- The end of the Template class ------------------- + + + +def jsEscapeString(s): + """ Escape s for use as a Javascript String """ + return s.replace('\\','\\\\') \ + .replace('\r', '\\r') \ + .replace('\n', '\\n') \ + .replace('"', '\\"') \ + .replace("'", "\\'") \ + .replace("&", '\\x26') \ + .replace("<", '\\x3C') \ + .replace(">", '\\x3E') + # Note: non-ascii unicode characters do not need to be encoded + # Note: previously we encode < as <, etc. However IE6 fail to treat