The - Split Expense - feature was introduced in odoo/odoo#90770 In this commit we fix the following bug, related to it: Steps to reproduce: - Create expense with tax_ids. - Click on - Split expense on the expense form. From the first hr.expense.split line remove the tax_ids. Rename it as '1', so that it is easier to find it back for checking later on. - Click on - Expense split on the wizard. Check the resulting expenses. Specifically, the one with the name '1'. Current behavior - The tax_ids field for the first expense (with the name '1') is still populated. Expected - The tax_ids field for the first expense should be empty. On top of that, we introduce the tests that check Split Expense flow. task - 2831024 closes odoo/odoo#108049 X-original-commit: 3aaf4f1ee2967793c9a4c29766cec63d2c6e3cf4 Related: odoo/enterprise#35005 Signed-off-by: Kevin Baptiste <kba@odoo.com>
66 lines
2.5 KiB
Python
66 lines
2.5 KiB
Python
# -*- coding: utf-8 -*-
|
|
# Part of Odoo. See LICENSE file for full copyright and licensing details.
|
|
|
|
from odoo.addons.account.tests.common import AccountTestInvoicingCommon
|
|
from odoo.addons.mail.tests.common import mail_new_test_user
|
|
|
|
|
|
class TestExpenseCommon(AccountTestInvoicingCommon):
|
|
|
|
@classmethod
|
|
def setUpClass(cls, chart_template_ref=None):
|
|
super().setUpClass(chart_template_ref=chart_template_ref)
|
|
|
|
group_expense_manager = cls.env.ref('hr_expense.group_hr_expense_manager')
|
|
|
|
cls.expense_user_employee = mail_new_test_user(
|
|
cls.env,
|
|
name='expense_user_employee',
|
|
login='expense_user_employee',
|
|
email='expense_user_employee@example.com',
|
|
notification_type='email',
|
|
groups='base.group_user',
|
|
company_ids=[(6, 0, cls.env.companies.ids)],
|
|
)
|
|
cls.expense_user_manager = mail_new_test_user(
|
|
cls.env,
|
|
name='Expense manager',
|
|
login='expense_manager_1',
|
|
email='expense_manager_1@example.com',
|
|
notification_type='email',
|
|
groups='base.group_user,hr_expense.group_hr_expense_manager',
|
|
company_ids=[(6, 0, cls.env.companies.ids)],
|
|
)
|
|
|
|
cls.expense_employee = cls.env['hr.employee'].create({
|
|
'name': 'expense_employee',
|
|
'user_id': cls.expense_user_employee.id,
|
|
'address_home_id': cls.expense_user_employee.partner_id.id,
|
|
'address_id': cls.expense_user_employee.partner_id.id,
|
|
})
|
|
|
|
cls.product_zero_cost = cls.env['product.product'].create({
|
|
'name': 'General',
|
|
'default_code': 'EXP_GEN',
|
|
'standard_price': 0.0,
|
|
'can_be_expensed': True,
|
|
})
|
|
|
|
|
|
# Allow the current accounting user to access the expenses.
|
|
cls.env.user.groups_id |= group_expense_manager
|
|
|
|
# Create analytic account
|
|
cls.analytic_plan = cls.env['account.analytic.plan'].create({'name': 'Plan Test', 'company_id': False})
|
|
cls.analytic_account_1 = cls.env['account.analytic.account'].create({
|
|
'name': 'analytic_account_1',
|
|
'plan_id': cls.analytic_plan.id,
|
|
})
|
|
cls.analytic_account_2 = cls.env['account.analytic.account'].create({
|
|
'name': 'analytic_account_2',
|
|
'plan_id': cls.analytic_plan.id,
|
|
})
|
|
|
|
# Ensure products can be expensed.
|
|
(cls.product_a + cls.product_b).write({'can_be_expensed': True})
|