Test were moved to RenderJS's repository.

This runTestSuite uses "python setup.py test" to launch the tests at
a certain folder.

The runTestSuite can upload results using TaskDistribution.

This code is generic enough to be used by others libraries.

The code on ERP5TypeTestSuite is preserved for backward compatibility for
now, until it got updated.

Update now, force the reload of all alarm promises.

Ser periodicity_hour to 0 in addition with "everyday" frequency

Instead raise an exception, try..except to log incapability of resolve the algorithm

Update copyright, license and xml changes on erp5_workflow business template

This exception is required to be used in ZODB due erp5_promise.

The UI created use "Check Consistency" Name in other to keep compatibility with future implementations which are going to use Constraints and checkConsistency API.

In other to keep the promise, create an System Preference if no other were setupped.

Sometimes on configuration product-config can be defined but promise-path and
site id isn't, like for example when some instance use DeadlockDebugger.

Whitespaces shall be encoded with %digit

Those alarms read the promise parameters (configured for example by SlapOS) and
can configure ERP5 if user want to solve the difference.

  Read external promise parameters.

  The parameters should be provided by an external configuration file.
  Location of this configuration file is defined in the zope configuration
  file in a product_config named as the path of the ERP5 site.
  Example if the site id is erp5:
    <product-config /erp5>
      promise_path /tmp/promise.cfg
    </product-config>

  The promise configuration is a simple ConfigParser readable file (a list of
  section containing a list of string parameters.

  getPromiseParameter returns None if the parameter isn't found.

regenerate test_document/Foo_001.odg with a recent LibreOffice so that it passes OpenDocument v1.2 Relax NG Schema.

raise NotImplementedError in WebSite_createWebSiteAccount so that it is not executed actually, because it is just an example of the implementation.

partially revert 5a53f57a because still many templates are using odf 1.0 or 1.1.

Improve default Discussion Thread Module view.

While installing a BT5 make sure not to install duplicate keys for the following ZSQLCatalog properties:
 - sql_catalog_search_keys
 - sql_catalog_related_keys
 - sql_catalog_scriptable_keys
 - sql_catalog_role_keys
 - sql_catalog_local_role_keys

Remove code duplication and make it easy to override how the key should be modified at install time.