Monday, September 12, 2022
5 changes · master
Enhancements to existing features
The resource form now places the resource type field below the company field. This small layout improvement makes the form easier to read and keeps related business information in a more logical order.
Original PR description
task-2971572
Sales menu ordering has been adjusted so existing entries are spaced farther apart. This makes it easier for add-ons or custom modules to insert new menu items in the right place without disrupting the standard layout.
Original PR description
Menu sequence of the sale module are now numbered 10/20/30 instead of 1/2/3 to allow third-party modules to introduce a new menu entry between two existing menu entries. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Website test tours have been standardized so they start from the website preview in a consistent way. This improves the reliability of automated checks across website-related apps, reducing false failures when pages or editing mode take longer to load.
Original PR description
*: test_website, website_blog, website_crm, website_event, website_forum, website_hr_recruitment, website_mass_mailing, website_sale, website_sale_wishlist, website_slides - Make sure that all…
Common testing checks for Odoo views were moved into a shared base test class. This makes it easier for teams to add and validate new view types with less duplicated test code, without changing end-user behavior.
Original PR description
The goal is to easily re-use these 3 common methods for unit tests in module implementing new type of views, such as `web_cohort` Related to odoo/enterprise#31239
The manufacturing product lifecycle document board was updated to work with the newer interface framework. This helps keep the document view compatible and reliable as the broader system evolves, with little visible change for users.
Original PR description
See odoo/odoo#99769
*: test_website, website_blog, website_crm, website_event, website_forum, website_hr_recruitment, website_mass_mailing, website_sale, website_sale_wishlist, website_slides - Make sure that all website tours reaching the website preview before their first step use the related website util to register their tour. - Rename the website util to register a tour starting on the website preview from `registerEditionTour` to `registerWebsitePreviewTour`. Having a method using "Edition" in its name and having a boolean parameter named `edition` was a bit... strange. - For both non edit mode and edit mode as a first step, ensure the util sets a high timeout for the first step. Indeed loading both the backend and the frontend (in the iframe) and potentially starting the edit mode can take a long time in automatic tests. We'll try and decrease the need for this high timeout of course. - Review the implementation of those utils to be more consistent and also fix one or two mistakes in them.