openerp-community-leaders team mailing list archive

["P. Christeas" <p_christ@xxxxxx>]

Following the discussions we're having these days about l10n_xx modules, 
accounting features and legal requirements, I believe that the local 
integrators and the community have to follow a trivial rule[1]:

 * All legal requirements for a country should be codes as (YAML) tests. *

.. well, not strictly YAML, but any of the supplied mechanisms could do.

The point is that whenever sth. is changed in the rest of OpenERP, the whole 
thing should be tested against these cases (requirements).

Example (from Dr. Gassauer): whenever some invoice or account.move is posted, 
that entry shall never be allowed to change, or even the partner's "law-
scoping" details (such as company name, VAT no., I suppose) should be locked 
down. 
 --> write a yaml test that generates an invoice, and then tries to hack the 
details in several ways. Ensure that all attempts fail [2].

Tests may be more important than the python code of the addons, itself. 
Because, tests will make sure the code is ok and won't disappoint our 
customers. 
In some countries, it is a legal requirement, indeed, to run those tests and 
prove (through them) that the ERP is obeying the law.

To OpenERP SA's developers, these tests will be a good guide to know that we 
are not breaking some country's logic. Sometimes, better than skimming through 
endless discussions to find out what happened to each country's integration.


[1] It must not be a new idea. But I wanted to remind everybody of it.
[2] in such a common case, we could put the test somewhere central, so that 
several countries can reuse the same code. I hope.


-- 
Say NO to spam and viruses. Stop using Microsoft Windows!