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

V2.5.0 Release Testing @ Stock Movement Workflow: Prescriptions #6141

Closed
13 tasks done
Tracked by #5679
marthakeezy opened this issue Jan 17, 2025 · 1 comment
Closed
13 tasks done
Tracked by #5679

V2.5.0 Release Testing @ Stock Movement Workflow: Prescriptions #6141

marthakeezy opened this issue Jan 17, 2025 · 1 comment
Assignees
Labels
Build Tested: Issues Found Issue has been build tested with new issue(s) made for failed tests. Release Testing For Release Testing issues, created for testing suites Tester: Maria

Comments

@marthakeezy
Copy link

marthakeezy commented Jan 17, 2025

Prescriptions

  • Before testing Prescriptions, take note of an item you are testing and take down the quantity - for example, I am testing Mebendazole Chewable Tablets 100mg.
  • When creating a new Prescription, add an item you are testing -> as soon as you press 'OK', the status of the prescription is going to change from New to Picked. At this point, the item quantity is going to go down under Catalogue -> Items and Inventory -> View Stock. Under Inventory -> View Stock, you can click on a batch you prescribed and under Ledger you should be able to see the stock movement with Prescription set as Type.
  • Changing the quantity prescribed, adding another batch or deleting a prescription should reverse the changes displayed under Catalogue -> Items and Inventory -> View Stock.
  • Confirming prescription as Verified should not have any further changes on the item quantity and you should not be able to edit the prescription either.

When backdating

Injection
22/02/2024: 50
07/03/2024: -10
15/03/2024: -20
21/03/2024: -10
22/03/2024: +50
Total on hand (at the moment): 60

The logic is to allow the users to backdate prescriptions without messing up the actions that were done afterwards. For example, let's say on 23d of February you had 60 items in stock. But 50 items were dispensed through time up until today, so actually you only have 10 items available to dispense. So if you were backdate the prescription to 23d of February, the system should only allow you to dispense 10 items and not 60.

  • Issuing 60 today should be allowed by the system ✅
  • Issuing 60 on 23d of February should not be allowed by the system 🚫 (because 50 items get dispensed through time until today's date, so in reality you only have 10 items to dispense). The system should give you an error and reset the date to today.
  • Issuing 10 on 23d of February should be allowed by the system ✅
  • Issuing 60 on 23d of March should be allowed by the system ✅
  • Issuing 61+ packs should not be allowed, in the past or now 🚫 (because it's more than you ever have in stock)
  • If you try and add another item to the prescription, and the stock for it is not available on the date you set previously, the system should give you an error and not allow to add 🚫

Make sure to test not only recently created prescriptions (e.g. if you create one on the day you are testing), but also repeat the actions for prescriptions that have been created previously and have been in the system for a few days/weeks.

  • Should not be able to edit a finalised prescription

Ledger

  • Prescription is New/Picked: creating a Prescription and adding an item to it will be reflected in the Ledger as Type: Prescription
  • Prescription is Verified: stays the same as above - reflected in the Ledger as Type: Prescription
@marthakeezy marthakeezy changed the title Prescriptions V2.5.0 Release Testing @ Stock Movement Workflow: Prescriptions Jan 17, 2025
@marthakeezy marthakeezy self-assigned this Jan 17, 2025
@marthakeezy marthakeezy added Release Testing For Release Testing issues, created for testing suites Tester: Maria Build Tested: Issues Found Issue has been build tested with new issue(s) made for failed tests. labels Jan 17, 2025
@marthakeezy
Copy link
Author

Raised quite a few bugs that I linked in this comment, including one hotfix -> #6162

Otherwise build test done in V2.5.0-RC4, moving to Done ✅

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Build Tested: Issues Found Issue has been build tested with new issue(s) made for failed tests. Release Testing For Release Testing issues, created for testing suites Tester: Maria
Projects
None yet
Development

No branches or pull requests

1 participant