Skip to content

[19.0][MIG] l10n_us_partner_legal_number: Migration to 19.0#177

Draft
dnplkndll wants to merge 8 commits into
OCA:19.0from
ledoent:19.0-mig-l10n_us_partner_legal_number
Draft

[19.0][MIG] l10n_us_partner_legal_number: Migration to 19.0#177
dnplkndll wants to merge 8 commits into
OCA:19.0from
ledoent:19.0-mig-l10n_us_partner_legal_number

Conversation

@dnplkndll
Copy link
Copy Markdown

Migration of l10n_us_partner_legal_number to Odoo 19.0.

lk-eska and others added 7 commits May 28, 2026 21:21
Closes the missing-tests/ HIGH finding from the OCA review. Adds 5 test
methods covering the constraint that gates the module's value:

- test_valid_ein_accepted (NN-NNNNNNN format)
- test_valid_ssn_accepted (NNN-NN-NNNN format)
- test_canadian_business_number_accepted (9 digits + check digit)
- test_invalid_legal_id_raises (garbage string → UserError)
- test_blank_legal_id_allowed (field is optional)

All examples picked to pass python-stdnum's validators (e.g. CBN
123456782 has a valid Luhn check digit, SSN avoids the 666/9XX/00
blacklisted ranges).

Pattern mirrors l10n_us_account_routing/tests/test_routing_number_bank.py.
@dnplkndll dnplkndll force-pushed the 19.0-mig-l10n_us_partner_legal_number branch from 045ce11 to f7f1fd9 Compare May 29, 2026 01:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

mod:l10n_us_partner_legal_number Module l10n_us_partner_legal_number series:19.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants