How to Test and Validate Custom Odoo Modules Before Deployment

Introduction: The "Works on My Machine" Syndrome

Every Odoo developer has said it. "It works on my local server." But when the module hits production, the server crashes, accounting entries don't post, or the warehouse scanner goes blank.

In the Odoo ecosystem, testing is often skipped because deadlines are tight. But skipping validation is false economy. This guide provides a robust Testing Framework for Odoo developers and QA leads, covering everything from automated unit tests to final user validation.

Level 1: Automated Unit Testing (The Developer's Responsibility)

Catch logic errors before they leave your laptop.

Odoo has a built-in testing framework based on Python's unittest. You don't need external tools; you just need discipline.

1. The TransactionCase Strategy

This is the bread and butter of Odoo testing. It runs a test in a transaction and rolls it back at the end, keeping your database clean.

Example: Testing a "Commission" Calculation

Create test file: tests/test_commission.py

from odoo.tests.common import TransactionCase

class TestCommission(TransactionCase):
    
    def setUp(self):
        super(TestCommission, self).setUp()
        self.sale_order = self.env['sale.order'].create({
            'partner_id': self.env.ref('base.res_partner_1').id
        })
    
    def test_commission_calculation(self):
        # Action: Add a line for $100
        self.sale_order.order_line = [(0, 0, {
            'product_id': self.product.id,
            'price_unit': 100.0
        })]
        
        # Assertion: Commission should be 10% ($10)
        self.assertEqual(
            self.sale_order.commission_amount,
            10.0,
            "Commission calculation failed"
        )

2. Running Tests Locally

Don't wait for the server. Run this command:

./odoo-bin -c odoo.conf -d test_db -i my_module --test-enable --stop-after-init

Level 2: Integration Testing (Tours & UI)

Does the button actually work?

Unit tests check code; Integration tests check workflows. Odoo uses "Tours" (JavaScript tests) to simulate a real user clicking through the interface.

How to Write a Tour:

Level 3: The CI/CD Pipeline (The Gatekeeper)

Automate the quality gate.

You should never manually deploy code. Use a Continuous Integration (CI) pipeline (GitHub Actions or Odoo.sh) to block bad code.

The Odoo.sh Workflow:

Level 4: User Acceptance Testing (UAT)

The final human check.

Automated tests can't check "usability." Only a human can tell you if a flow is annoying or confusing.

The UAT Protocol:

Level 5: Post-Deployment Validation (Sanity Check)

Did we break anything else?

After deploying to Production, run a "Sanity Check" immediately.

tail -f /var/log/odoo/odoo-server.log | grep -E "(Traceback|Error)"

Testing Levels Summary

Frequently Asked Questions

Conclusion: Quality is a Process

Testing isn't an "extra step"; it is part of development. By implementing a pipeline that includes Unit Tests, Tours, and human UAT, you turn deployment day from a stressful event into a non-event.