Check global consistency in configurator tests
Use `portal_alarms/check_consistency` after configuration to make sure that every document created by configurator or part of the dependency business template is valid. For now we have two exceptions (that are some TODO for the future): - Web Sites, because upgrader constraints are not ran by configurator at this point - Business Configuration, because most of the configurator item classes don't fully follow the protocol of constraints, their `fixConsistency` method always return "something needs to be fixed" without actually checking. See merge request !1562
Status | Job ID | Name | Coverage | ||||||
---|---|---|---|---|---|---|---|---|---|
External | |||||||||
passed |
#341964
external
|
ERP5.CodingStyleTest-Master |
|
||||||
passed |
#341965
external
|
ERP5.PerformanceTest-Master |
00:26:52
|
||||||
failed |
#341969
external
|
ERP5.UnitTest-Master |
|
||||||
failed |
#341968
external
|
ERP5.UnitTest-Master.Medusa |
|
||||||
passed |
#341961
external
|
SlapOS.Eggs.UnitTest-Master.Python2 |
|
||||||
passed |
#341962
external
|
SlapOS.Eggs.UnitTest-Master.Python3 |
|
||||||