domains / families / software-engineering / odoo-automated-tests

odoo-automated-tests

authentic

Write and run Odoo automated tests using TransactionCase, HttpCase, and browser tour tests. Covers test data setup, mocking, and CI integration.

When to use

• Writing unit tests for a custom model's business logic.
• Creating an HTTP test to verify a controller endpoint.
• Debugging test failures in a CI pipeline.
• Setting up automated test execution with `--test-enable`.

When not to use

• **JavaScript tour tests** require a running browser (via `phantomjs` or `Chrome headless`) and a live Odoo server — not covered in depth here.
• `HttpCase` tests are significantly slower than `TransactionCase` — use them only for controller/route verification.
• Does not cover **mocking external services** (e.g., mocking an SMTP server or payment gateway in tests).
• Test isolation is at the **transaction level**, not database level — tests that commit data (e.g., via `cr.commit()`) can leak state between tests.

Skill page

Source