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

Define Functional Test Scenarios for the core engine and its preceeding order management #229

Open
6 of 8 tasks
ben3474 opened this issue Jan 8, 2025 · 0 comments · May be fixed by #245
Open
6 of 8 tasks

Define Functional Test Scenarios for the core engine and its preceeding order management #229

ben3474 opened this issue Jan 8, 2025 · 0 comments · May be fixed by #245
Assignees
Labels

Comments

@ben3474
Copy link

ben3474 commented Jan 8, 2025

The pre-requisite is to have the demo data installed (localized in Switerland) and purchase/sales/invoice/sustainability. All the sustainability modules have to be installed.

  • Test 1
    Title : Carbon computation at invoice level (Carbon on Invoice)
    Objective : Verify that if a weight is defined at invoice line level, it stays at this level without looking at the rest of the preceeding order
    Data : FACTU/2025/01/0002
    Expected result : +450 kgCO2e *** computation level = "Carbon on invoice" *** #lines within carbon.line.origin model = 3

  • Test 2
    Title : Carbon computation at product's level
    Objective : Verify that without weight at invoice line level and for a product having an emission factor defined, it uses it
    Data : RFAC/2025/00002
    Expected result : +3882.6 kgCO2e *** computation level = "Product" *** #lines within carbon.line.origin model = 7

  • Test 3
    Title : Carbon computation at product's category level
    Objective : For the same product as the one used in the Carbon on Invoice test, verify that without weight at invoice line level, it rolls up at product category level
    Data : RFAC/2024/00003
    Expected result at invoice line level for product "FURN_6741": +300.6 kgCO2e *** computation level = "Product category" *** #lines within carbon.line.origin model = 3

  • Test 4
    Title : Carbon computation at supplier's level with a monetary emission factor
    Objective : Verify that without weight at invoice line level and for a product not having any emission factor defined and nothing defined at category level, it uses the underlying chart of account's emission factor.
    Data : FACTU/2025/01/0003
    Expected result at invoice line level for account 6000001 : +49 (rounded at 0 dp) kgCO2e *** computation level = "Partner" *** #lines within carbon.line.origin model = 1

  • Test 5
    Title : Carbon computation at account's level with a monetary emission factor
    Objective : Verify that without weight at invoice line level and for a product not having any emission factor defined and nothing defined at category level nor at supplier's level, it uses the underlying chart of account's emission factor.
    Data : Need to create a demo data sample. Similar invoice as that one "FACTU/2025/01/0003" except that it must be for another vendor as Azure Interior has already an EF defined at partner level.
    Expected result :

  • Test 6
    Title : Carbon computation at company's fallback level with a monetary emission factor
    Objective : Verify that without weight at invoice line level and for a product not having any emission factor defined and nothing defined at category level nor at supplier's level and nothing defined at account level, it uses the underlying company's fallback's emission factor.
    Data : FACTU/2023/10/0001
    Expected result : +5306.80 (rounded at 2 dp) kgCO2e *** computation level = "Company fallback" *** #lines within carbon.line.origin model = 3

  • product template

  • res.partner

@ben3474 ben3474 added the test label Jan 8, 2025
@ben3474 ben3474 assigned BonnetAdam and jacopobacci and unassigned BonnetAdam Jan 9, 2025
@jacopobacci jacopobacci linked a pull request Jan 21, 2025 that will close this issue
@jacopobacci jacopobacci linked a pull request Jan 21, 2025 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants