A PO must be in state cancel to be canceled.
Before the fix, it was possible to cancel a draft PO
then if a PO linked to a procurement was deleted with being
canceled, the procurement stayed in running state.
opw:666311
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
* rfq2order2done - test case of process RFQ->confirm RFQ->Done RFQ.
* generate_invoice_from_reception - test case of process to generate invoice on delivery of product.
* run_scheduler - test case of process to run scheduler to generete RFQ from procurement.
* merge_order - test case to merge orders
* cancel_order - test case to cancel confirmed order, draft order
* print_report - test case to generate report of RFQ and purchase order.
* onchange_events - test case to test onchange_events like onchange_partner, onchange_warehouse, onchange_address
* duplicate_order - test case to test duplicate order.
* delete_order - test case to test delete confirmed order, draft order and canceled order.
bzr revid: hmo@tinyerp.com-20111020072225-jq2r5x70z12a15o8
Goffin Simon