Use Odoo Enterprise modules in test with OCA tools

[OpenCode]

Hi @sbidoul. Do you have any suggestions or examples on how to add Odoo enterprise modules among available modules for testing in Github Action?

Originale request here: #23 (comment)

[sbidoul]

@OpenCode I don't have step by step instructions for that...

I mentioned one approach in #23: If you can bring odoo/enterprise in the test image, you can simply update the Odoo addons-path in (the) $ODOO_RC (file) to point to it. Pip install of addons is compatible with addons path and you can mix both..

If you can git clone enterprise it in the GitHub action, that should be relatively easy?

For our projects we pin and package odoo (with the help of odoo/odoo#44001), enterprise and our customer addons (with setuptools-odoo or hatch-odoo) as wheels that we pip install before running the tests.

Let me know if there are specifics you want to discuss.

[AungKoKoLin1997]

@sbidoul I tried to git clone enterprise in GitHub action. But there is a problem that is checking version for enterprise addons.

[sbidoul]

You'll need to set correct version numbers for the modules you want to test with this image.

[AungKoKoLin1997]

@sbidoul I set correct version number for my custom modules that are in my private repo. But the issue is not from my private repo. Some of modules are depend on enterprise modules and I don't want to fail CI tests. That's why I tried to clone odoo enterprise addons in the test image. But unfortunately, version is also checked for enterprise modules in the install addons and dependencies step. In the above image, partner_commission is a enterprise module and checking version. Was my approach wrong?

[AungKoKoLin1997]

Sorry. I used addons_dir instead of addons_path. Now my tests is succeed but I think this approach is not good way to use in organization repo because we need to use token to clone enterprise addon in test image.