Monday, May 19, 2025
3 changes · saas-18.1
Resolved issues and error corrections
This fix updates an internal sales and inventory test so it consistently has the right permissions to check product packaging fields. It helps prevent false test failures during module validation, improving release reliability without changing customer-facing behavior.
Original PR description
This commit ensures that the group `uom.group_uom` is correctly applied on the test user, so that the tour doesn't fail on the step looking for "Packagings" field on the product view which happened in some [single module tests](https://runbot.odoo.com/odoo/runbot.build.error/222678). --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fix makes automated checks for favorite search management more reliable by using predictable test data and confirming that page updates have finished. It helps prevent false failures in testing without changing day-to-day user behavior.
Original PR description
Because of commit https://github.com/odoo/odoo/commit/b5ba14bc77a12268e5ce1e2a7aa7e48ba209f876 tours are faster and don't wait much between two steps. Also, when removing or adding a facet in the search view, there is no way to determine that the subsequent reload has been done. The factet is removed or added immediately, the reload happens after. So, before the refactoring of macro.js, we waited a little bit longer, allowing the reload of the view to be done before going to the next step. This commit mitigates this by making the dataset of the tour more dterministic in order to be able to check that in the DOM. It is possible that the problem occurs in 18.0 as well, so feel free to backport this fix. runbot-error-162145
This change makes an automated test for message notification sounds more reliable by allowing enough time for message updates to load. It helps reduce false test failures in Odoo's mail area without changing the user experience.
Original PR description
Before this commit, the `message sound on receiving new message` was sometimes failing. It occurs because the test uses the `waitFor` web method to wait for the message unread counter to change. However, `waitFor` has a much smaller timeout than `contains` (200ms vs 3s). In this particular scenario, receiving the bus notification, fetching the channel and rendering the chat hub initially can take a little bit more time than 200ms, making the test fail. This commit increases the time out to match the `contains` one for this test. fixes runbot-159866 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