Daily updates from Odoo
Wednesday, February 28, 2024
3 changes · 17.0
Enhancements to existing features
This update adjusts the performance test thresholds in the mail module to match the latest system benchmarks. The changes ensure that performance tests accurately reflect current system capabilities and prevent false test failures due to outdated baseline metrics.
Original PR description
Based on last runbot counters
This update cleans up and standardizes translations across all Mexico-specific modules by refreshing translation files, backporting v17 translations, and consolidating to use Spanish (es.po) instead of Mexico-specific variants. This ensures users in Mexico have consistent and complete translations throughout the system.
Original PR description
A lot of translations were missing from the l10n_mx* localizations therefore they are cleaned up by: - re-exporting all of the pot files of the modules starting with l10n_mx* (most were out of date…
A lot of translations were missing from the l10n_mx* localizations therefore they are cleaned up by: - re-exporting all of the pot files of the modules starting with l10n_mx* (most were out of date and/or incorrectly manually modified) - the translations from v17 are backported (a bunch update of all of the terms in these modules was done for v17) - the modules were all consistently updated to use es.po only, i.e. es_MX.po files were removed, since both were used but in v17 they were all converted to es_419 (i.e. the default Spanish local from v17 onwards) Notes: - This was only done in saas-16.3 onwards to support a ticket. Previous versions can have similar steps done for them when requested by customers, but are not done as part of this PR because it's cumbersome to do. - Since terms change between versions, probably some translations are missing and can be added in as demanded/noticed by customers (since it's also cumbersome to track them down) opw-3452127 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#155262 Forward-Port-Of: odoo/odoo#155214
This update adds comprehensive tests for the email template system used in event communications, particularly for batch email sending to event attendees. The changes improve test reliability and maintainability by refactoring email scheduler tests and adding new test coverage for registration-time communications. This ensures the email system works correctly as the team prepares to optimize batch email processing.
Original PR description
PURPOSE Mail: add tests for MailTemplate send_mail Several flows use MailTemplate.send_mail() in batch, notably event email scheduler which sends emails to event attendee in batch. This commit adds…
PURPOSE
Mail: add tests for MailTemplate send_mail
Several flows use MailTemplate.send_mail() in batch, notably event email
scheduler which sends emails to event attendee in batch. This commit adds
tests around 'send_mail' method of MailTemplate model
* add tests for batch: it is currently not supported hence using a loop but
batch is going to be added soon, allowing to test the batch version works
as intended;
* add query counters, notably for batch mode and when dynamic reports are
involved in templates;
Event: improve mail scheduler tests
Make them easier to improve and modify
* use a dedicated setup (allowing to add specific unit tests on test data);
* move initial asserts into its own unit test (to keep other tests shorter);
* use available mocks for freezetime and sql.now;
Then add tests for registration emails, to check what happens for communication
scheduled right at registration time.
LINKS
Part of Task-3764894: Event: Allow using cron triggers for communication
Part of Task-3764891: Mail: Batch-ize MailTemplate send_mail
Part of Task-3164278: Mail: Batch send: ensure limit, avoid force
Part of Task-3084943: Event: Improve communication scheduler scalability