[ADD] Fixture environment

[ssaid]

No description provided.

[guewen]

You should surround the environment with a odoo.api.Environment.manage(): context manager:

with odoo.api.Environment.manage():
    yield odoo.api.Environment(cr, uid, {})

[dcrocco]

@guewen I think this fixture is pretty usefull for bdd with pytest-bdd, want me to re-open this with this?:

@pytest.fixture(scope='session', autouse=True)
def env():
    db_name = odoo.tests.common.get_db_name()
    registry = odoo.registry(db_name)
    cr = registry.cursor()
    with odoo.api.Environment.manage():
        env = odoo.api.Environment(cr, odoo.SUPERUSER_ID, {})
        yield env
    registry.clear_caches()
    registry.reset_changes()
    env.reset()
    cr.rollback()
    cr.close()

[guewen]

If it has autouse=True, it means it will always be used right? Can you explain me what does it change compared to the current behavior and what would this fixture bring (which use case?)?

[dcrocco]

Yes, but it will run only once.

I’m using it when i need the odoo enviroment and i’m not inheriting from odoo test clases, for example when doing integration tests cross-modules (in my case i’m using pytest-bdd, and i need it for a lot of scenarios).

Else, you will always need to inherit from odoo test classes or set up this in every scenario.

What do you think?

[simahawk]

This has been created a loooong time ago. Is it still relevant?