- 20 Oct, 2017 1 commit
-
-
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 !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 !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 4 commits
-
-
Vincent Bechu authored
/reviewed-on nexedi/erp5!453
-
Gabriel Monnerat authored
-
Jérome Perrin authored
To make predicate lookup a bit faster by keeping `predicate` and `predicate_category` small, do not index the documents we do not need in these table. This is done for `Assignment`, `Career`, `Payment Condition`, `Delivery Cells`, `Budget Line` and `Budget Cells`. /cc @vpelletier @kazuhiko @tiwariayush /reviewed-on nexedi/erp5!257
-
Jérome Perrin authored
ERP5's Code mirror supports viewing history of editions using codemirror's merge mode ( http://codemirror.net/demo/merge.html ). This was enabled for portal_components, but not for web pages. This moves the methods used by the components in a mixin class and make `TextDocument` class use this mixin. This way, we can benefit from diff view on web pages as well: ![ERP5-history-on-web-pages](/uploads/2bd381948266da46225ae26fd807bd51/ERP5-history-on-web-pages.png) @romain @vincentB @katomaso unless this interfere with your work of making codemirror works in renderjs ui, I think we can enable this. It does not include any change to codemirror code, just enable everywhere what was available only on components. @klaus I did not check, but we probably want this enabled for PyData Script as well. /reviewed-on nexedi/erp5!449
-
- 13 Oct, 2017 13 commits
-
-
Tristan Cavelier authored
-
Tristan Cavelier authored
keep backward compatibility with erp5_officejs_support_request_ui
-
Tristan Cavelier authored
- fails if 0 - fails if too much - also applied for predecessor
-
Tristan Cavelier authored
-
Tristan Cavelier authored
keep backward compatibility with erp5_officejs_support_request_ui
-
Tristan Cavelier authored
keep backward compatibility with erp5_officejs_support_request_ui
-
Jérome Perrin authored
It was "dead code", this form was not used in any action. Fields were not following naming conventions, so search would not even work. Because we generate search dialogs based on module listbox, organisation module already had a working search dialog, so this dialog is not needed anymore.
-
Vincent Bechu authored
Prevent syncro fail on frozen document Ignore Remove attachment or document for erp5
-
Vincent Bechu authored
-
Vincent Bechu authored
Prevent issue when document is edited in multiple tab.
-
Vincent Bechu authored
And adapt cache
-
Vincent Bechu authored
To be consistant with date format in hateoas And follow Javascript default format https://developer.mozilla.org/fr/docs/Web/JavaScript/Reference/Objets_globaux/Date/parse
-
Vincent Bechu authored
-