During tests, some creation of user records would unnecessarily trigger
password reset or set a password, both of which would trigger password
hashing which takes some time (for good reasons).
Fix by:
* passing no_reset_password in YAML tests and some Python tests still
missing it (a number of Python tests already used it)
* removing passwords from YAML records as they're never necessary, the
test user records are not expected to ever log in
Sales Order lines have a cancelled state, but this state is not
always considered when looping over lines. This check is
done in some places already and this patch's aim is to do it in the
remaining places.
- Cancel the procurement of a sale line in sale.order.line
instead of sale.order, so a line canceled individually with
sale_order_line.button_cancel will properly cancel it
procurement.
- Sale report: uses the state of lines instead of Sales order,
so canceled lines of not-canceled orders are correctly represented
in the analysis.
- test: do not create invoices lines for canceled sale lines
- test: creation of moves with canceled lines
- test: check if lines are still canceled when sale order is done
Closes#6036
A squashed merge is required as the conversion of the apiculture branch from
bzr to git was not correctly done. The git history contains irrelevant blobs
and commits. This branch brings a lot of changes and fixes, too many to list
exhaustively.
- New orm api, objects are now used instead of ids
- Environements to encapsulates cr uid context while maintaining backward compatibility
- Field compute attribute is a new object oriented way to define function fields
- Shared browse record cache
- New onchange protocol
- Optional copy flag on fields
- Documentation update
- Dead code cleanup
- Lots of fixes
Having a static boolean field is a mess and requires
a lot of custom code to make sure it is up-to-date,
implying a large source of possible bugs.
Using a function field should take care of updating
it when needed.
All the write() calls that were updating it were
normally removed, and there was also some cleanup
in the surrounding areas (quite minimal).
bzr revid: odo@openerp.com-20121129162629-5lt9e0v5aju36itj
- `delay` field on SO line moved to sale_stock, ignoring it for now
- avoid reusing the same bank account in 6.1 test, would cause a test
failure because the import would be skipped and the new partner
would have no bank account. Bank accounts should be unique in the
real world.
- log in DEBUG when a relationship record is skipped during EDI import
bzr revid: odo@openerp.com-20121019111100-dwf0crocqv43m3ij
The EDI documents will now be generated on demand
and available from the Portal view of each document.
Instead of getting a link to a statically generated
EDI document, customers will receive a link to
the portal access to the document. They will be able
to signup on the portal the first time as well,
provided they are using the secure token that was
sent to them (i.e. the right link).
The link to pay online will be available in the
portal as well.
Still much to do, this is a small first step,
with edi.document renamed to edi.edi for
consistency, as it will not persist any
edi.document anymore.
bzr revid: odo@openerp.com-20121011152008-bht7ub6woaex0a7u
Xavier Morel
Alexandre Fayolle
Guewen Baconnier
Raphael Collet
Christophe Matthieu
Christophe Simonis
Olivier Dony
Martin Trigaux
sgo@tinyerp.com
Foram Katharotiya (OpenERP)
Vo Minh Thu
Tejas Tank
Ajay Chauhan (OpenERP)
Quentin (OpenERP)
Atul Patel (OpenERP)
Rucha (Open ERP)