by human interaction.

Each workflow should use the respective Zuite.

Check the lock files, and launch the xvfb with some available display.

Use ERP5TypeFunctionalTestCase and runUnitTest instead of runFunctionalTest

O directly use the browser for manual runs.

The Configurator is usually used to bootstrap some instance, so have
previous business templates may cause some inconsistent.

Reorganize to execute tutorial tests for each configuration.

This make code of bt5 a bit smaller

Phantomjs still draft.

Make code more generic and several clean ups and API definititions.

Several changes which only improve code readability only.

It's job of form validation to handle this case appropriately.

modify Person object it can still unblock it if it has access to system
events).

Unknown ids must not prevent to create a document, so let ERP5 compute new ids.

Create (and open Assingmnet) before validating Person object.

change authentication cookie as well at client side in same transaction.
This way a logged in user is able to change current password without
being kicked out of the system within.

API.
Adjust test accordingly.

change events.
Adjust test accordingly.

use email.utils.formataddr instead of '"%s" <%s>' to support double-quotes and backslashes correctly.

use email.utils.formataddr instead of '"%s" <%s>' to support double-quotes and backslashes correctly.

We might want to rely on MailHost for filling those fields.