summaryrefslogtreecommitdiff
path: root/addons/base_address_extended/tests
AgeCommit message (Collapse)Author
2021-05-16[FIX] base_address_extended: split 'correctly' street nameNasreddin Boulif (bon)
Issue - Install "Contacts" & 'base_address_extended' modules - Go to contacts and create a contact with value: - street name : Chaussee de Namur - House : 40 - Save and edit again - Set country to 'Netherlands' then save. Address not splited well (wrong values for street name and house). The issue is not present in UI but is in tests. (Issue in UI from odoo 14.0+) Cause There is 2 '_split_street_with_params' (inverse function that set street fields): - partner_autocomplete_address_extended (removed in 14.0) - base_address_extended The 'spliting' logic is not the same in both function. In UI, looks like it does not call '_split_street_with_params' from 'base_address_extended' since no super(Partner, self)... However in testing, it does call it from module 'base_address_extended' and therefore trigger the issue. Solution Adapt _split_street_with_params function (in 'base_address_extended' module): If previous field (from 'street_format') to parse in 'street_raw' is 'street_name', then: - set `tmp` to: splitted (max 1 split) street_raw with current field seperator - set `append_previous, sep, tmp[0]` to: splitted tmp[0] (first part of splited street_raw) with `rpartition(' ')` - add 'append_previous' to 'street_name' value - join 'tmp' values and set it to street (should equal to what left from `rpartition(' ')` split + seconf part of first normal split) - continue normal parsing flow opw-2476096 closes odoo/odoo#70783 X-original-commit: d094d2646023965cb3254a31ee8f59aabaf7f2ea Signed-off-by: bon-odoo <nboulif@users.noreply.github.com>
2020-01-07[REF] base_address_extended: clean and improve testsThibault Delavallée
Purpose is to make tests easier to understand and more data oriented. We now understand more clearly what is an input and what is expected. Tests about company / partner address fields are added to ensure coherency. Task ID 2158302 PR odoo/odoo#42678
2019-11-05[IMP] base_address_extended: Adapt tests to work with/without demo dataYannick Tivisse
2018-12-13[FIX] base_address_extended: add missing mexican address formatJulien (juc) Castiaux
After this fix, the field `partner.street` is correcly rendered, but as the test shows the `street_name` and `street_number` fields are not correct. But as there are tests that validate that wrong use case, I consider it a *feature* and not a bug. opw-1896773 closes odoo/odoo#29520
2018-07-23[FIX] base_address_extended: Changing country on a partnerGoffin Simon
Steps to reproduce the bug: 1. Create a Vendor with these address settings - Name: Vendor123 - Streer" Street: - Housnumber: 123 >> DO NOT ADD A COUNTRY => by default street_format = street_number street_number2 street_name 2. Create a purchase order for Vendor123 3. print the RFQ >> ADDRESS FORMAT "123 Street" => OK 4. Go to vendor123 and set "Netherlands" as a country 5. Print RFQ again Bug: >> The address was still in format "123 Street" => NOT OK When changing the country on a partner, the field street must be recomputed because the street_format depends on the country. opw:1865677
2017-04-28[FIX] Various P3-related import changesxmo-odoo
* LDAP import: python-ldap is not python3-compatible, pyldap is Warning: only supported from debian Stretch (current testing)? https://packages.debian.org/search?searchon=names&keywords=pyldap * implicitly relative imports * imports of moved or removed stdlib modules issue #8530
2016-12-28[ADD] base_address_extended: add module to take care of multiple fields ↵qdp-odoo
inside the 'street' fields defined in base