Do it litearally as otherwise it would require or monkeypatching Sequence.

Even more: some test might generate inconsistent objects, so such approach
will give flexibility.

But keep simple assertion.

WARNING: this is an quick ugly hack to not block developper.
The clean fix is to swith to the rest API defined in:
http://packages.python.org/slapos.core/

vifib_open_trade is required before vifib_slap.

vifib_open_trade provides portal type configured by vifib_slap.

Test for bug_module/20120103-128245F

It will allow to export them as RSS, so add erp5_rss_style dependency.
It reuses erp5_knowledge_pad methods, so add it as dependency.

variation property which comes from Item generates getVariationPropertyList.
VariationRange's property defines variation_property which also generates
getVariationPropertyList

As there is conflict which is not solved by category accessor generation
sorting (which is per property sheet) adding later VariationRange will result
in overwriting accessor for category with own one.

variation property which comes from Item generates getVariationPropertyList.
VariationRange's property defines variation_property which also generates
getVariationPropertyList

As there is conflict which is not solved by category accessor generation
sorting (which is per property sheet) adding later VariationRange will result
in overwriting accessor for category with own one.

There shall be no inconsistent documents after any tic.

Periodicity like original one (on Sunday).

Configured to check all objects (no module restriction, no additional query)
and to send notification in case of problem.

Thanks to calling builders on tic and calling this alarm directly, real issues
of incorrecting building are always exposed.

Activities can be called randomly, so instead of registering building process
invoke it.

They are called in any moment, between tics. So trigger builder during tic in
order to be closer to real site.

Missing object.