Before, postgres configuration was hardcoded. This worked OK for OCA's CI infrastructure, but failed in any other out there that had different defaults.
There's no need to hardcode it; Odoo already must have Postgres connection settings, so let's use those instead. This will make tests testable across different CI infrastructures.
base_external_dbsource 12.0.1.0.1
[UPD] Update base_external_dbsource.pot
Update translation files
Updated by "Update PO files to match POT (msgmerge)" hook in Weblate.
Translation: server-backend-12.0/server-backend-12.0-base_external_dbsource
Translate-URL: https://translation.odoo-community.org/projects/server-backend-12-0/server-backend-12-0-base_external_dbsource/
[UPD] Update base_external_dbsource.pot
Update translation files
Updated by "Update PO files to match POT (msgmerge)" hook in Weblate.
Translation: server-backend-12.0/server-backend-12.0-base_external_dbsource
Translate-URL: https://translation.odoo-community.org/projects/server-backend-12-0/server-backend-12-0-base_external_dbsource/
* Heavily refactor code for reusability
* Split all sources into independent modules
* Add more test coverage
* Add CRUD methods
* Add iterator execute return to roadmap
OCA Transbot updated translations from Transifex
* Migration of base_external_dbsource to odoo 9.0
* Fixing test error
* Moving test from yaml to python
* Fixing pylint error in test class
* Placeholder added to connection string text zone
* improving test coverage
OCA Transbot updated translations from Transifex
Cached methods should never return recordsets, which are tied to
specific context, env, cursor, uid. Instead, they should return IDs
which, later, can be browsed in the current context.
With this change _usable_rules() cached method is now returing ids instead
of a recordset, and also the _match_find method is properly browsing the
results ids of the cached method.
These 2 tests were checking the exact set of groups a user should have.
If these tests are ran in a database where a module is previously installed which adds more groups to the base role, these exact group sets would be inexact, although the behavior that is being tested was actually properly working.
With this patch, basically I'm testing if the user contains the groups from the roles, not the exact role set expected. It should work in integration scenarios.
@Tecnativa TT20468
