- 19 Oct, 2018 39 commits
-
-
Boris Kocherov authored
-
Boris Kocherov authored
-
-
-
-
Boris Kocherov authored
-
Boris Kocherov authored
-
-
Boris Kocherov authored
-
Boris Kocherov authored
-
Boris Kocherov authored
-
Boris Kocherov authored
-
Boris Kocherov authored
-
Boris Kocherov authored
-
Boris Kocherov authored
-
Boris Kocherov authored
-
Boris Kocherov authored
-
Boris Kocherov authored
-
Boris Kocherov authored
-
Boris Kocherov authored
-
Boris Kocherov authored
-
Boris Kocherov authored
-
Boris Kocherov authored
-
Boris Kocherov authored
-
Boris Kocherov authored
-
Boris Kocherov authored
erp5_web_renderjs_ui: html5_select: event option for notifyChange added. needs for determine event.type on parent gadget
-
Boris Kocherov authored
-
Boris Kocherov authored
-
Boris Kocherov authored
-
Boris Kocherov authored
-
Boris Kocherov authored
-
Boris Kocherov authored
-
Boris Kocherov authored
-
Boris Kocherov authored
-
Boris Kocherov authored
-
Boris Kocherov authored
-
Boris Kocherov authored
-
Boris Kocherov authored
i need it because use span for displaying icons in json form
-
Jérome Perrin authored
This is needed when running livetests in a runUnitTest instance, in the following scenario: - `runUnitTest --save test_bt:testXXX` - `runUnitTest --save --load` - run the live test from the browser because livetest way of processing activities is to unsubscribe at the beginning of the test and subscribe at the end to have control of activities when running .tic, if ProcessingNodeTestCase also process the activities automatically, they interfere and test often fail with errors like: ``` File "ERP5Type/tests/ProcessingNodeTestCase.py", line 249, in tic raise RuntimeError(error_message) RuntimeError: tic is looping forever. These messages are pending: [('/erp5/portal_components/test.erp5.testSupportRequest', 'immediateReindexObject', 1, 0), ('/erp5/support_request_module/2617', 'immediateReindexObject', -1, 0)] ``` /reviewed-on nexedi/erp5!779
-
- 17 Oct, 2018 1 commit
-
-
Jérome Perrin authored
This step just checks that multi relation field listbox shows a list of related document and that clicking on any item of the list leads to the related document. The order of related documents in the list has always been unspecified, but the first one was always 1 until recently. Because this test does not really care which one of the two related document was clicked, just assert that it's a document from foo_module. /reviewed-on nexedi/erp5!774
-