This new object has a bad id, we should change it. Also, may not be
in the good place in erp5_configurator_standard and should be
moved in another bt5.
The reason of his place in erp5_configurator_standard, is that
erp5_configurator_standard is automatically installed when
fix site consistency is done, thereby it install this preconfigured
object to. If this object is moved, the bt5 which will contains it
must be added to the list of bt5 to install when doing check site
consistency.

We only only need an usual test result proxy, we only need the additional
method getRunningTestCase

This commit in order to force the flush of files
containing test informations after each iteration.

Add option to specify several path where to find users file(s),
and benchmark suite file(s).

This runner is used by scalability test, it communicates
with ERP5 Master and launch test suite (using performance_tester).

Testnode code has been splitted. Runner class has been created for
each test types (unit and scalability).
Communication with SlapOS and ERP5 Master has been added.

These benchmarks are used during scalability tests.
A file which contains list of scalability users is also added.

Contain objects and scripts needed to perform scalability tests.

Allow to close a draft position.

trade model and invoice transaction line should be in same invoice

so that we can invoke same tests in our favourite collection of business templates by using this mixin.

We should also support the case where user cannot access project module

The same grouping reference property is also used for mirror section, so if one side is doing grouping, the group must also be valid for the other side.

Usually subscription item portal type does not have a proper tracking, so you may want to use this alarm only on some item portal types

In some configurations this might be incorrect, but for most cases it is not a
good idea that a price that is currently beeing edited gets applied.

At least this is the behaviour expected in my understand

This is required for ERP5Site_checkDataWithScript script (erp5_core BT).

This is not a new feature, this behavior is compatible with the old caching
implementation that was using inventory_stock table.
In other words, this brings backs the backward compatibility in inventory
caching.

(This commit fixes the incomplete tests that was reverted just before.)

Needs more tests.

This reverts commit 74db4d39.

This is not a new feature, this behavior is compatible with the old caching
implementation that was using inventory_stock table.
In other words, this brings backs the backword compatibility in invetory
caching.