Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[16.0][MIG] l10n_nl_account_tax_unece #377

Closed
wants to merge 16 commits into from

Conversation

astirpe
Copy link
Member

@astirpe astirpe commented Jan 20, 2023

@NL66278
Copy link
Contributor

NL66278 commented Jan 23, 2023

/ocabot migration l10n_nl_account_tax_unece

@OCA-git-bot OCA-git-bot added this to the 16.0 milestone Jan 23, 2023
@OCA-git-bot OCA-git-bot mentioned this pull request Jan 23, 2023
6 tasks
Copy link
Contributor

@bosd bosd left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM 👍

@astirpe astirpe force-pushed the 16_mig_l10n_nl_account_tax_unece branch from 23c8d2a to 7915daf Compare October 6, 2023 06:28
@astirpe
Copy link
Member Author

astirpe commented Oct 6, 2023

Rebased. Also changed license from AGPL to LGPL, so this PR now depends on OCA/community-data-files#172

@astirpe astirpe force-pushed the 16_mig_l10n_nl_account_tax_unece branch from 7915daf to ce3ec5a Compare October 31, 2023 11:13
@thomaspaulb
Copy link
Contributor

Hm, the test fails with

2023-10-31 11:15:43,571 268 ERROR odoo odoo.addons.l10n_nl_account_tax_unece.tests.test_nl_account_tax_unece: FAIL: TestNlAccountTaxUnece.test_existing_coa_update
Traceback (most recent call last):
  File "/__w/l10n-netherlands/l10n-netherlands/l10n_nl_account_tax_unece/tests/test_nl_account_tax_unece.py", line 63, in test_existing_coa_update
    self.assertTrue(tax.unece_type_id.id == unece_type_id)
AssertionError: False is not true

@astirpe
Copy link
Member Author

astirpe commented Nov 16, 2023

Seems the tests are failing after odoo/odoo@b63f21b since a new tax template "btw_X0_ABC_levering" was added in l10n_nl.

@bosd
Copy link
Contributor

bosd commented Nov 16, 2023

Please have a look at this PR, #404 to update the category's.
Maybe we can incorporate that, before the migration to V16.

@astirpe
Copy link
Member Author

astirpe commented Nov 16, 2023

@bosd yes indeed it could be fixed all-in-once. I will include your fixes but unfortunately I'm not able to verify myself whether they are correct or not.

@bosd
Copy link
Contributor

bosd commented Dec 30, 2023

Sorry, I forgot about that PR. Continued working on it..
Now ready for 14 and 15 branch.
When you include it here, it might fix the tests 🤔

@NL66278
Copy link
Contributor

NL66278 commented Jan 3, 2024

@astirpe So these are the two test failures, bot related to COA:

2023-10-31T11:15:43.5728662Z 2023-10-31 11:15:43,571 268 �[1;31m�[1;49mERROR�[0m odoo odoo.addons.l10n_nl_account_tax_unece.tests.test_nl_account_tax_unece: FAIL: TestNlAccountTaxUnece.test_existing_coa_update
2023-10-31T11:15:43.5730016Z Traceback (most recent call last):
2023-10-31T11:15:43.5731325Z   File "/__w/l10n-netherlands/l10n-netherlands/l10n_nl_account_tax_unece/tests/test_nl_account_tax_unece.py", line 63, in test_existing_coa_update
2023-10-31T11:15:43.5732615Z     self.assertTrue(tax.unece_type_id.id == unece_type_id)
2023-10-31T11:15:43.5733237Z AssertionError: False is not true
2023-10-31T11:15:43.5733662Z 

---

2023-10-31T11:15:47.0571298Z 2023-10-31 11:15:47,051 268 �[1;31m�[1;49mERROR�[0m odoo odoo.addons.l10n_nl_account_tax_unece.tests.test_nl_account_tax_unece: FAIL: TestNlAccountTaxUnece.test_load_coa
2023-10-31T11:15:47.0572735Z Traceback (most recent call last):
2023-10-31T11:15:47.0574052Z   File "/__w/l10n-netherlands/l10n-netherlands/l10n_nl_account_tax_unece/tests/test_nl_account_tax_unece.py", line 41, in test_load_coa
2023-10-31T11:15:47.0575279Z     self.assertTrue(tax.unece_type_id.id == unece_type_id)
2023-10-31T11:15:47.0575898Z AssertionError: False is not true
2023-10-31T11:15:47.0576306Z  

Instead of assertTrue and then an equal comparison, maybe better do an assertEqual. Then on failure you will have both values in the log, making it easier to get to the root of the problem.

@hbrunn
Copy link
Member

hbrunn commented Apr 15, 2024

superseded by #417

@hbrunn hbrunn closed this Apr 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants