- 25 Oct, 2017 9 commits
-
-
Romain Courteaud authored
Listbox can embed rjs gadget
-
Romain Courteaud authored
-
Romain Courteaud authored
It is no longer maintained. Switch to ck_editor instead.
-
Romain Courteaud authored
ung has been replaced by officejs.
-
Romain Courteaud authored
-
Romain Courteaud authored
This editor has been deprecated and is not supported anymore.
-
Romain Courteaud authored
This bt5 provides required portal types (Web Style, ...)
-
Romain Courteaud authored
This reverts commit 8076005e. Web Illustration is already provided by another bt5.
-
Cédric Le Ninivin authored
-
- 24 Oct, 2017 5 commits
-
-
Roque Porchetto authored
-
Roque Porchetto authored
-
Roque Porchetto authored
-
Roque Porchetto authored
-
Roque Porchetto authored
This business template contains all the objects needed to bootstrap an ERP5 instance in order to prepare it for scalability tests: - A business configuration object (generated after standard configurator installation) - A bootstrap script (pending) - A script that generates a specific amount of users (person-assignment-login per each)
-
- 20 Oct, 2017 3 commits
-
-
Vincent Pelletier authored
-
Vincent Pelletier authored
-
Vincent Pelletier authored
The main change here is the reduction of try..except scope, so failing the first assertion does not cause an AttributeError about original_query. Also, avoid code duplication by just checking final number of messages outside the try..except block. Also, improve coding style (spaces around operators and commas). Also, avoid single-use variable. Also, fix typo in comment.
-
- 19 Oct, 2017 5 commits
-
-
Tristan Cavelier authored
to fit to the new behavior related to these changes : - 2c74e408 - a40266af
-
Tristan Cavelier authored
-
Julien Muchembled authored
Commit 89a17f04 broke live tests using ERP5TypeTestCase.publish when they are run from command line. Note that such live test could not be run from ERP5. More refactoring is needed because ERP5TypeLiveTestCase should only take care of adapting ERP5TypeTestCaseMixin to an ERP5 environment, and runUnitTest should never use it. Commit fd9219af looks a wrong approach.
-
Sebastien Robin authored
Usually, the split and defer dialog suggest you to define start and stop date. So if you have already an existing delivery and you would like it to be updated, you have to set correct start and stop date and, if all categories are fully the same, you might have some chance to see this delivery updated. To improve the case where you would like to move quantity to existing delivery, add option in the solve divergence dialog of "Move to existing Delivery" that allows you to select similar deliveries. Then this specific solver would set correct properties for you to make sure the expected delivery would be updated.
-
Cédric Le Ninivin authored
-
- 18 Oct, 2017 6 commits
-
-
Julien Muchembled authored
A change that also applies to traditional tests is that the password does not need to be known when logging with basic authentication. If the given password is empty (e.g. 'ERP5TypeTestCase:'), password validation passes regardless the actual password: to keep things secure, this exception is only valid for the test thread and during the call to publish(). This is a simple way to deal with random passwords in live tests.
-
Cédric Le Ninivin authored
-
Cédric Le Ninivin authored
-
Cédric Le Ninivin authored
* For the purpose of easy customisation
-
Jérome Perrin authored
We use internal transactions for invoices and any kind of accounting transactions (in reality, it's not limited to *invoice*), this is a set of changes to make it easier to record payments between two entities with internal transactions. * We add a *Section Bank Account* field directly on the view ( ![Screenshot_2017-10-04_at_19.36.53](/uploads/4b1f22b5d5e6c1f77a70ea717c2323d9/Screenshot_2017-10-04_at_19.36.53.png) * Reconfigure *Causality (Invoices ...)* relation fieds to allow allow every accouting transactions portal type, so also Internal Invoice Transaction ..."). This way, when creating the "payment" internal transaction, we connect it to the "invoice" internal transaction and grouping reference is set automatically when posting to general ledger. * Enable the *Create Payment* action from (which exists on sales and purchase) on normal invoices. The rest is small cleanup / fixes described in commit messages. /reviewed-on nexedi/erp5!433
-
Jérome Perrin authored
Various improvements to `CodingStyleTestCase` so that it can be used in a project test suite. /reviewed-on nexedi/erp5!455
-
- 17 Oct, 2017 11 commits
-
-
Sebastien Robin authored
Usually, the split and defer dialog suggest you to define start and stop date. So if you have already an existing delivery and you would like it to be updated, you have to set correct start and stop date and, if all categories are fully the same, you might have some chance to see this delivery updated. To improve the case where you would like to move quantity to existing delivery, add option in the solve divergence dialog of "Move to existing Delivery" that allows you to select similar deliveries. Then this specific solver would set correct properties for you to make sure the expected delivery would be updated.
-
Nicolas Wavrant authored
when form is used in another context (web section for exemple).
-
Cédric Le Ninivin authored
-
Vincent Bechu authored
/reviewed-on nexedi/erp5!456
-
Jérome Perrin authored
-
Jérome Perrin authored
Not used in this test, but since it's made to be reusable in projects.
-
Jérome Perrin authored
-
Jérome Perrin authored
do not limit to the first script with errors
-
Jérome Perrin authored
It produces almost same visual result
-
Jérome Perrin authored
they may contain folder containing skins
-
Jérome Perrin authored
Don't test a skin folder twice when business template is present more than once
-
- 16 Oct, 2017 1 commit
-
-
Vincent Bechu authored
/reviewed-on nexedi/erp5!453
-