Odoo Changelog — 2019-11-06

Wednesday, November 6, 2019

2 changes

Improvements(2)

Enhancements to existing features

[IMP] account: Disable disabled test

Coremasteraccount

This change disables a problematic accounting test that was already marked as disabled. It helps keep development and validation workflows stable while the underlying test issue can be addressed separately.

Original PR description

Description of the issue/feature this PR addresses:

Current behavior before PR:

Desired behavior after PR is merged:




--
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

#accounting#testing#stability

[MERGE] various: Make the test suite demo data independant

PR #6509

Enterprisemasteraccount_3way_matchaccount_accountantaccount_assetaccount_bank_statement_import_camtaccount_bank_statement_import_ofxaccount_batch_paymentaccount_budgetaccount_followupaccount_online_syncaccount_plaidaccount_sepaaccount_sepa_direct_debit

The test suite was updated so accounting-related tests create the data they need instead of depending on preloaded demo records. This makes future demo data changes safer, improves test speed, and supports more reliable validation across migrated databases.

Original PR description

Purpose
=======

This is the first huge step to improve the test suite in several ways:

- Make them demo data independent, allowing to modify the demo data without having to adapt the tests depending on it. It also allows to have a beautiful + convenient demo dataset to make a demonstration, and to configure complex data in the tests to manage the corner cases.
- Improve the test performances by converting them into SavepointCase. Each test will be rollbacked to it's initial state, after the setUpClass call. That way the different data are not re-created at each test for nothing.
- Introduce several test classes in base/tests/common.py to launch a TransactionCase, HttpCase or SavepointCase test with an available demo user, portal user or a large set of partners.
- This is the first step to tend to a rolling release process, allowing to execute the tests (or a subset of the tests) on a migrated base, for example.

TaskID: 2075739

#testing#demo-data#reliability#performance

Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

Purpose ======= This is the first huge step to improve the test suite in several ways: - Make them demo data independent, allowing to modify the demo data without having to adapt the tests depending on it. It also allows to have a beautiful + convenient demo dataset to make a demonstration, and to configure complex data in the tests to manage the corner cases. - Improve the test performances by converting them into SavepointCase. Each test will be rollbacked to it's initial state, after the setUpClass call. That way the different data are not re-created at each test for nothing. - Introduce several test classes in base/tests/common.py to launch a TransactionCase, HttpCase or SavepointCase test with an available demo user, portal user or a large set of partners. - This is the first step to tend to a rolling release process, allowing to execute the tests (or a subset of the tests) on a migrated base, for example. TaskID: 2075739