- 24 Sep, 2020 2 commits
-
-
Jérome Perrin authored
Round the amounts line by line when validating transactions balances and showing the totals on an accounting transaction. Even though float field configurations do not allow users to input transactions where amounts uses more digits that what makes sense for the selected currency, we had cases where some transactions generated by custom scripts were "too precise" and passed the validation because unlike in all reports where we display sum of rounded values, the check was only rounding the sum, which cause some transactions with 1.00 on one side and 0.333333 0.333333 and 0.333333 on the other side to be valid. The scripts used to display sums on an accounting transaction had the same problem, they were also showing the rounded sum and not the sum of rounded values.
-
Jérome Perrin authored
Always use textwrap.dedent implicitly so that we don't have to do it in every test and disable the way of making multi lines scripts by passing multiple arguments. Now there's only one way to do and every tests use the same way
-
- 23 Sep, 2020 4 commits
-
-
Jérome Perrin authored
getRepositoryList contain all business template repositories, ie: ['/srv/slapgrid/slappart4/srv/slapos/soft/c63ba7265399450b28f9ea6d5667a5e7/parts/erp5-doc/bt5', '/srv/slapgrid/slappart4/srv/slapos/soft/c63ba7265399450b28f9ea6d5667a5e7/parts/erp5/bt5', '/srv/slapgrid/slappart4/srv/slapos/soft/c63ba7265399450b28f9ea6d5667a5e7/parts/erp5/product/ERP5/bootstrap', '/srv/slapgrid/slappart4/srv/slapos/soft/c63ba7265399450b28f9ea6d5667a5e7/parts/erp5-bin/bt5'] it seems in random order. Test was written to use the one from parts/erp5/bt5, but since it just takes "anything which does not contain bootstrap" it was sometimes getting erp5-bin or erp5-doc and could not find erp5_configurator_standard business template. Change the selection of the repository to take into account that we may also have erp5-doc and erp5-bin and so that it fails if more than one.
-
Jérome Perrin authored
all member of random module are available (because in ZopeGuards, there's a random.__allow_access_to_unprotected_subobjects__ = 1), SystemRandom class also is, but Random class was not, even though there should be nothing unsafe in this. This is needed if we want to use a random number generator with a fixed seed to get reproductible results. We could use random.seed module level function but since this is also used by several things in ERP5 this does not produce reproductible sequences.
-
Jérome Perrin authored
See merge request nexedi/erp5!1265
-
Arnaud Fontaine authored
ZODB Components: TestZodbDocumentComponentReload (e5587493): No need to run other common Component tests.
-
- 21 Sep, 2020 3 commits
-
-
Romain Courteaud authored
-
Romain Courteaud authored
-
Romain Courteaud authored
-
- 18 Sep, 2020 3 commits
-
-
Nicolas Wavrant authored
-
Jérome Perrin authored
-
Jérome Perrin authored
Before we had the sub-documents exported as properties of container document for some reason. Now they are exported as separate documents, as expected.
-
- 17 Sep, 2020 7 commits
-
-
Kazuhiko Shiozaki authored
-
Jérome Perrin authored
-
Jérome Perrin authored
See merge request nexedi/erp5!1264
-
Jérome Perrin authored
runTestSuite accept a --test_node_title argument, which is used in createTestResult API call, so that task distributor can keep track of which node executed which task, but since it was not passed, we did not know which test node executed which test result line. See merge request nexedi/erp5!1205
-
Jérome Perrin authored
Remove some unused code and enable coding style See merge request nexedi/erp5!1263
-
Vincent Pelletier authored
-
- 16 Sep, 2020 11 commits
-
-
Georgios Dagkakis authored
Change the conditions from getAggregate to hasAggregate and add a portal_type filter of getPortalDocumentTypeList, since in reality these check for Attachments that are Document Types stored in ERP5, so types like 'Internet Message Post' should not be considered. Plus, xml changes, since there was no commit in these fields in the last 9 years
-
Roque authored
-
Arnaud Fontaine authored
-
Arnaud Fontaine authored
-
Arnaud Fontaine authored
-
Arnaud Fontaine authored
ZODB Components: Migration dialog: list_selection_name must be explicitly named for mapply() to pass it from REQUEST.
-
Arnaud Fontaine authored
-
Arnaud Fontaine authored
-
Arnaud Fontaine authored
-
Jérome Perrin authored
Payments made on the date of previous bank statement but not at 00:00 were not taken into account in this constraint, which leaded to false positive preventing to open the next bank reconciliation when previous one had a payment with an accounting date on the day of the bank statement but not at 00:00
-
Jérome Perrin authored
Instead of only checking that an error is reported, check the expected error message, so that we are sure that this test really covers what it's supposed to cover.
-
- 15 Sep, 2020 7 commits
-
-
Julien Muchembled authored
-
Jérome Perrin authored
Now that testnode client is supposed to pass test node title, make sure that on the server side we can display this information.
-
Jérome Perrin authored
runTestSuite accept a --test_node_title argument, which is used in createTestResult API call, so that task distributor can keep track of which node executed which task, but since it was not passed, we did not know which test node executed which test result line.
-
Jérome Perrin authored
-
Jérome Perrin authored
-
Jérome Perrin authored
-
Jérome Perrin authored
This was never finished and would probably not be implemented this way, so let's remove.
-
- 11 Sep, 2020 3 commits
-
-
Jérome Perrin authored
ERP5 functional tests are failing too often, until we improve the tests or the code so that we don't have these intermitent failures, restart the failed tests a bit automatically. This is of course not good, because it's hiding problems, but the current state of the test suite with many randomly failing test makes that we sometimes miss when permanent failures are introduced. See merge request !1206
-
Jérome Perrin authored
these actions are not ready to be used by end users
-
Jérome Perrin authored
Persons created before the introduction of ERP5 Login and user_id will only have a user_id after migration if they were already user before migration, otherwise they will not have a user_id and creating assignments and ERP5 Login for this person creates a user which can not log in the system. To make it possible for these persons to login anyway, we ensure person has a user id when validating a login This is bc67c2c4 again, but with a proxy role on the interaction workflow and a non regression test to cover the problem with the first version of that commit.
-