Wednesday, February 2, 2022
6 changes · master
Enhancements to existing features
This update improves Odoo's internal test setup so browser tests can better simulate touch-capable devices. It helps ensure features that rely on touch interactions are tested more accurately, reducing the risk of issues reaching users.
Original PR description
…adless 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
This change removes an unnecessary 5-second wait before browser-based tests begin. It makes debugging and running individual test suites quicker for developers, with no expected impact on regular users.
Original PR description
Since [1], the test suite waits for 5s to start running. It's really annoying when you run the suite in your browser, to debug a single test or a sub suite. Waiting for 5s to determine whether all modules can be loaded or not is not necessary anymore since all assets coming from the same bundle are loaded in a single file, even in debug=assets. This is true under the assumption that there's no js module in assets_common requiring a module in another assets bundle, which seems reasonnable. [1] 468eb84fb413c97d3ae101a7b639d4bac6d0231d 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
This update refreshes internal performance test expectations after recent improvements reduced database query counts. It also fixes a missed naming update in website sales and forum code so tests stay consistent and reliable.
The mail and snailmail interface dialogs were modernized to support upcoming framework changes. This helps keep message and attachment actions reliable while preparing the Discuss experience for future upgrades.
Original PR description
In preparation to using OWL 2 in discuss code. Task-2738648
SEPA Direct Debit payment notifications now reuse the payment transaction already being processed instead of searching for it multiple times. This improves processing efficiency and keeps payment validation behavior consistent.
Original PR description
Before this commit, most acquirers needed to run several successive searches for the transaction whose reference was received by a controller in notification data. This is because the security checks run on the notification data require access to the acquirer through the transaction record which was immediately discarded. Starting with this commit, all `*_feedback_data` method are no longer decorated with `api.model` and can use the transaction record they're called on if provided. They are also renamed to `*_notification_data`. task-2737144 See also: - https://github.com/odoo/odoo/pull/83850
The payroll accounting test suite for Belgium was adjusted to allow for a higher expected query count after related system changes. This is an internal maintenance update that helps keep automated tests aligned and does not change user-facing payroll features.
Original PR description
Title :) See odoo/odoo#76097 TaskId-2602897