Skip to content
This repository has been archived by the owner on Mar 31, 2021. It is now read-only.

Void sales invoice and invoice the billing candidates again #132

Closed
3 of 4 tasks
metas-dh opened this issue Jun 16, 2019 · 0 comments
Closed
3 of 4 tasks

Void sales invoice and invoice the billing candidates again #132

metas-dh opened this issue Jun 16, 2019 · 0 comments
Assignees
Labels
branch:master branch:release depends-on:printing Tasks which need to print a document, but printing support is not implemented yet in cypress Fixtures:Updated Prio:1 Topic: Accounting Topic:Sales
Projects

Comments

@metas-dh
Copy link
Member

metas-dh commented Jun 16, 2019

Relates to

Test shall include:

  • Customer Fixtures to use: (if needed)
  • What to test
  • Expectation for the test to be successful

http://recordit.co/kBCRmbto7t

Note:
You need a sales invoice, created from billing candidates.

Todo for developer (besides coding)

All Flags are ticked? Congratulations, you have delivered!

Steps

Create Sales Order

  • complete
  • referenced doc "shipment disposition"

Shipment Disposition

  • expect only 1 line
  • select action - Generate shipments
    • Quantity to deliver
    • Complete shipment note: true
    • Shipment date today: false
    • wait for notification: "Lieferung [number] fur partner [the bpartner] wurde erstellt."
      • read all notifications

Back to the Sales Order

  • Referenced doc "Invoice Disposition" (goes to "Billing Candidates")

Billing Candidates

  • expect 1 line
  • expect ordered = same as SO
  • expect bpartner; shipped qty; product = same as SO
  • expect qty invoiced = 0
  • actions - generate invoices
    • nur fur = false
    • rechnungs = false
    • supplement = true
    • date; accounting date; order reference = empty
      • expect notification: "Rechnung [number] fur Partner [the bpartner] wurde erstellt."
  • expect qty invoiced = same as SO
  • click the notification to be taken to the Sales Invoice

Sales Invoice 1

  • should not be paid
  • should have same total as SO
  • set status "Void"
    • it should become "Reversed"
    • it should become Paid now

Back to the Sales Order

  • there should be 2 Referenced "Sales Invoice"
  • one has positive total amount, the other has negative total amount (but equal to the positive value)

Back to the Sales Order

  • Referenced doc "Invoice Disposition" (goes to "Billing Candidates")

Billing Candidates (the second time)

  • expect 1 line
  • expect qty invoiced = 0
  • actions - generate invoices
    • nur fur = false
    • rechnungs = false
    • supplement = true
    • date; accounting date; order reference = empty
      • expect notification: "Rechnung [number] fur Partner [the bpartner] wurde erstellt."
  • expect qty invoiced = same as SO

Sales Invoice 2

  • should not be paid
  • should have same data as SO
  • should have same total as SO

Main points:

  • voided invoice becomes "Reversed" & "Paid"
  • billing candidates can be invoiced a 2nd time after the 1st invoice was voided, without any problems
  • 2nd invoice has the same values as the 1st, since nothing was changed in the billing canidate(s)
  • billing candidates afterwards has relations to both invoices in referenced documents (overall there are 3 invoices now, bc the voiding process creates a counterpart invoice to the 1st one, with neg. qties, also "Reversed" & "Paid", but the main part of this test is that the billing candidates can be invoiced correctly again)
@metas-dh metas-dh added this to To do in e2e via automation Jun 16, 2019
@metas-dh metas-dh moved this from To do to Data Prepared in e2e Jun 16, 2019
@TheBestPessimist TheBestPessimist self-assigned this Jul 4, 2019
@TheBestPessimist TheBestPessimist moved this from Data Prepared to In progress in e2e Jul 15, 2019
@TheBestPessimist TheBestPessimist added the depends-on:printing Tasks which need to print a document, but printing support is not implemented yet in cypress label Jul 15, 2019
TheBestPessimist added a commit that referenced this issue Jul 17, 2019
TheBestPessimist added a commit that referenced this issue Jul 17, 2019
TheBestPessimist added a commit that referenced this issue Jul 17, 2019
TheBestPessimist added a commit that referenced this issue Jul 17, 2019
TheBestPessimist added a commit that referenced this issue Jul 17, 2019
TheBestPessimist added a commit that referenced this issue Jul 17, 2019
TheBestPessimist added a commit that referenced this issue Jul 17, 2019
…didn't work when doing the action `Void` which sets the status to `Reversed`

#132
TheBestPessimist added a commit that referenced this issue Jul 17, 2019
TheBestPessimist added a commit that referenced this issue Jul 17, 2019
TheBestPessimist added a commit that referenced this issue Jul 17, 2019
TheBestPessimist added a commit that referenced this issue Jul 17, 2019
TheBestPessimist added a commit that referenced this issue Jul 17, 2019
TheBestPessimist added a commit that referenced this issue Jul 17, 2019
TheBestPessimist added a commit that referenced this issue Jul 17, 2019
TheBestPessimist added a commit that referenced this issue Jul 17, 2019
TheBestPessimist added a commit that referenced this issue Jul 17, 2019
…didn't work when doing the action `Void` which sets the status to `Reversed`

#132
TheBestPessimist added a commit that referenced this issue Jul 17, 2019
TheBestPessimist added a commit that referenced this issue Jul 17, 2019
TheBestPessimist added a commit that referenced this issue Jul 17, 2019
TheBestPessimist added a commit that referenced this issue Jul 17, 2019
TheBestPessimist added a commit that referenced this issue Jul 17, 2019
TheBestPessimist added a commit that referenced this issue Jul 17, 2019
TheBestPessimist added a commit that referenced this issue Jul 17, 2019
TheBestPessimist added a commit that referenced this issue Jul 17, 2019
…` XHR to finish before checking changed status

#132
@TheBestPessimist TheBestPessimist moved this from In progress to To be reviewed in e2e Jul 17, 2019
e2e automation moved this from To be reviewed to Done Jul 18, 2019
metas-ts added a commit to metasfresh/metasfresh that referenced this issue Jul 22, 2019
  * [#5364](#5364) BPartner REST-API - Add Support for additional core fields
  * [#5390](#5390) Add Quality Issue warehouse filter in Warehouse list page
  * [#5370](#5370) Introduce more webui WidgetSizes (XL, XXL)
  * [#2304](metasfresh/metasfresh-webui-frontend-legacy#2304) Picking Terminal (Prototype): not all picking slots not displayed / close when clicking outside
  * [#2307](metasfresh/metasfresh-webui-frontend-legacy#2307) Set precision to 2 digits for `CableLength` field
  * [#46](metasfresh/metasfresh-e2e-legacy#46) Create test: warehouse
  * [#121](metasfresh/metasfresh-e2e-legacy#121) Create new Stock Control Purchase
  * [#126](metasfresh/metasfresh-e2e-legacy#126) Create Empties Receive
  * [#129](metasfresh/metasfresh-e2e-legacy#129) Create Dunning Candidates
  * [#130](metasfresh/metasfresh-e2e-legacy#130) Create Dunning Documents
  * [#132](metasfresh/metasfresh-e2e-legacy#132) Void sales invoice and invoice the billing candidates again
  * [#162](metasfresh/metasfresh-e2e-legacy#162) Create credit memo Vendor (Lieferant)
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
branch:master branch:release depends-on:printing Tasks which need to print a document, but printing support is not implemented yet in cypress Fixtures:Updated Prio:1 Topic: Accounting Topic:Sales
Projects
e2e
  
Done
Development

No branches or pull requests

4 participants