Friday, February 9, 2024
3 changes · saas-17.1
Enhancements to existing features
JavaScript test suites can now send key progress details directly to runbot build pages. This makes it easier for teams to spot missing or slow test runs without digging through full technical logs.
Original PR description
The purpose of this PR is to allow to write a log from a JS test with the RUNBOT level.
That way a JS test could write useful information that will be available on the runbot build page.
By convention, a JS `console.dir` will be converted into a python loglevel `RUNBOT` (25) instead
of a simple `INFO`.
e.g.:
`console.dir('15 tests passed');`
will lead to a log on a runbot build page like:
`15 tests passed`
(with the usual meta information)This update makes cache invalidation activity easier to track in production once the system registry is ready. It helps technical teams investigate and optimize performance without changing business workflows.
Original PR description
before this commit, ormcache invalidation was only logged in the debug mode. This commit allows ormcache invalidation to be logged when the registry is ready in production, which helps developers to trace/optimize ormcache invalidation. 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
Financial reports now use shorter labels for journal, analytic, and options filters, helping users see and navigate report controls more easily. This improves the reporting interface by saving space, especially in crowded report headers.