🌱 V2.5.0 Release Testing

[marthakeezy]

V2.5.0 Release Testing 🌱

Note

Test Scripts are available here, they are updated as the new features are coming out ✍🏼

Note

Please follow this document for the most up-to-date QA practices :)

v2.5.0 NEW FEATURES

• V2.5.0 Release Testing: GEDSI #5884
• V2.5.0 Release Testing: GEDSI #5884 Dev Test - @CarlosNZ
• V2.5.0 Release Testing: CIV Program Internal orders #5981
• V2.5.0 Release Testing: CIV Program Internal orders #5981 Dev Test - @lache-melvin
• V2.5.0 Release Testing: Dispensing Enhancements #5931
• V2.5.0 Release Testing: Dispensing Enhancements #5931 Dev Test - @roxy-dao
• V2.5.0 Release Testing: Reports #5885
• V2.5.0 Release Testing: Reports #5885 Dev Test - @jmbrunskill

WORKFLOWS

These can be either one-store or multiple-store setup; depending on the workflow.
Priority is to make sure the stock movement is functioning

STOCK MOVEMENT WORKFLOWS

Dev Test - @noel-yeldos ✅ (only #6029)

• V2.5.0 Release Testing @ Stock Movement Workflows: Inventory Adjustments / Item Ledger #6029
• V2.5.0 Release Testing @ Stock Movement Workflows: Inbound and Outbound Shipments #6076
• V2.5.0 Release Testing @ Stock Movement Workflow: Inbound and Outbound Returns #6115
• V2.5.0 Release Testing @ Stock Movement Workflows: Repacks #6126
• V2.5.0 Release Testing @ Stock Movement Workflow: Stocktakes #6136
• V2.5.0 Release Testing @ Stock Movement Workflow: Prescriptions #6141

NORMAL ORDERING WORKFLOWS

Dev Test - @zachariah-at-msupply ✅

• V2.5.0 Release Testing @ Normal Ordering Workflow: Creating/Placing Internal Orders #6105
• V2.5.0 Release Testing @ Normal Ordering Workflow: Receiving Customer Requisitions #6106
• V2.5.0 Release Testing @ Normal Ordering Workflow: Supplying through Outbounds #6183
• V2.5.0 Release Testing @ Normal Ordering Workflow: Receiving through Inbounds #6184

SYNCHRONISATION: CENTRAL DATA SYNC & SYNC INTEGRATION

Dev Test - @Chris-Petty [#6135 ✅ ]

• V2.5.0 Release Testing @ Test: Central Data Sync & Sync Integration #6173

GENERAL MODULES

These can be tested in a single-store environment since they're more focused on UI
Priority is to check/test if no buttons/modules are broken

DISTRIBUTION

• V2.5.0 Release Testing: Outbound Shipments #6169
• V2.5.0 Release Testing: Requisitions #6206
• Inbound Returns
• Customers

REPLENISHMENT

• Inbound Shipments
• Internal Orders
• Outbound Returns
• Suppliers

CATALOGUE

• Assets
• Items
• Master Lists

INVENTORY

Dev Test - @fergie-nz ✅

• Locations
• Stocktakes
• Stock

DISPENSARY

• Patients
• Prescriptions
• Encounters

SETTINGS

Dev Test - @aimee-mcneil-melville ✅

• Display settings
• Sync
• Support
• Devices

SYNCHRONISATION

• Installation
• Initialisation
• Synchronisation
• Reinitialisations
• Version-updates

CUSTOMISATIONS

COLD CHAIN

• Monitoring
• Sensors
• Equipment

MANAGE IMMUNIZATIONS

• Configuration
• Facilities
• Demographics

IMMUNIZATIONS PROGRAMS

Dev Test - @GeronimoJohn ✅

• Immunizations Programs

PATIENT PROGRAMS

Dev Test - @andreievg ✅

• Patient Registration
• Patient List
• Patient Details View
• Patient Program Enrolment
• Patient Program Encounters
• Viral Load logic
• Lost to Follow up (LTFU)

PROGRAM REQUISITIONS

• Setups
• Creating a Program Internal Order
• Program IO Window
• Requisitions

REMOTE AUTHORISATION

• Creating Internal Order
• Approving Internal Order
• Supplier Requisition

[alainsussol]

Tracking of issues found during release testing

• V2.5.0 Release Testing: Dispensing Enhancements #5931
  • Prescription: Unable to remove Clinician's name  #5977
  • Prescription: 'S' appearing for item with no units #5978
  • No Alert when trying to backdate prescription #6014
  • Unable to backspace the item selection when issuing prescriptions #6047
  • Prescriptions: Unit Quantity calculation is wrong if the item's Pack Size is higher than 1 #6059
  • When dispensing multiple batches of the same item, ledger's balance groups them together instead of showing changes per line #6060
  • 'Line Already Exists' error when changing the quantity dispensing for the first time in a prescription #6061
  • Sometimes the backdated prescription date does not change - user does not get a warning #6158
  • In Stock and Available show wrong numbers once the prescription is saved #6162
  • Prescription's status does not get updated back to 'New' if the items get deleted/removed #6164
  • Able to interact with the 'Directions' field in a prescription even if can't add the item #6165

• V2.5.0 Release Testing: GEDSI #5884
  • GEDSI: logout modal text is too close/overlaps #5886
  • GEDSI: revoked user permissions come back when changing languages #6006
  • GEDSI: When store is set to Portuguese, clicking on Help -> User Guides shows the page in English #6011
  • GEDSI: contact us form running into an error #6016
  • GEDSI: some buttons on Android blur together with the background (missing shadow?) #6161

• V2.5.0 Release Testing: CIV Program Internal orders #5981
  • There are 2 scroll bars in the item list of the internal order edit window #6021
  • Extra fields in IO should use Use consumption and clients stock data in internal orders pref #6019
  • Hide the text "Nothing Here" when there is nothing to show as item stats in the internal order line edit window #6050
  • Internal order indicator default value is -0 for numbers #6068
  • On internal order using the "Use suggested quantities" button will erase all previously requested quantities you have put in #6069
  • You can create more than the max number of emergency internal orders by period defined for a program. #6144
  • The internal order indicators values doesn't show on the corresponding requisition of the supplier store when both the supplier and customer are on omSupply #6145
  • For Ivory Coast, Indicators should not be included in emergency orders #6146
  • Indicators details show Nothing here where there is no customer to show. This text should be hidden #6147
  • When creating an program internal order, the number of instances of the same supplier shown in the supplier list is sometimes greater than 1 and the number change when you type to search #6148

• V2.5.0 Release Testing: Reports #5885

  • Standard requisition Report Issues #6081
  • Report Headers don't line up with table (when no logo configured) #6094
  • Stocktake Variance Report fails with missing cost prices #6095
  • Stocktake Variance Report - Shows big decimal numbers... #6096
  • Stocktake with quantity and without quanity seem to be wrong way around? #6097
  • Packsize shows as Pack in reports?  #6098
  • For the stocktake_reports and generally for all reports, it would be good if columns headers should be printed on every page instead of only the first one. #6187
  • Wrong column header for target Stock in requisition report #6192

• Miscellaneous

  • Inbound shipment does round decimals in for cost and sell prices #6002
  • Sync icon is not updated to white colour, only visible when hovered over the button #6005
  • Some areas of omSupply briefly disappear upon refreshing, causing fidgety UI #6007
  • Not a user friendly error showing when deleting a Stock Transfer inbound shipment #6018
  • Typo in the error when trying to add a patient and the registry does not exist #6030
  • Changes to the item's cost and sell prices get reflected in the item's historic ledger entries #6040
  • Stocktake print templates content is misaligned and hard to read #6041
  • Printing Templates need improvement #6043
  • Column headers need improvement/rethinking 💭 #6046
  • Inbound Shipment printout does not include taxes #6055
  • Incorrect Created Date, Confirmed Date and Shipped Date when printing out an Inbound/Outbound Shipment #6056
  • Creating customer returns from outbound shipments does not take user to the newly created return page #6062
  • Supplier Return modal goes blank if you take too long to action #6064
  • Placeholder lines can provide more details #6074
  • 'Invoice Number' column can be clearer #6075
  • User has to double-click 'Next' when adding items to Internal Orders #6079
  • Internal Order log event showing 'Requisition created'  #6080
  • Unclear which store's SOH & AMC are shown when clicking on an item in Requisitions #6086
  • The current workflow for creating a customer return does not allow to calculate 'total before tax' properly #6118
  • Getting confirmation pop-up about any unsaved changes even if no changes have been made #6132
  • Internal order editing requested packs does not save changes #6128
  • Internal order pressing "Next" while adding a new item can navigate to undefined/infinite spinner #6119
  • Duplicated error when trying to delete a locked stocktake #6137
  • Should we have 'On Hold' as a status option for Stocktakes? #6138
  • Store becomes incredibly slow when a big stocktake is generated #6139
  • Custom patients: able to save patients with required fields empty #6160
  • Updating any stockline field leads to cost price being updated even if it wasn't changed -> decimal number reduction #6163
  • Future date is coloured red when issuing batches in Outbound Shipments #6182
  • On the internal order Info panel what I am writing disappear after I wrote it #6188
  • Outbound Shipments created from Customer Requisitions don't have Pack Qty Issued column prepopulated #6196
  • Able to add items to a non-manual requisition #6199
  • Graph in Requisitions seems to be showing inaccurate Stock on Hand numbers #6208
  • Name filter does not work in Requisitions #6215
  • Item's ID briefly appears when adding an item to a manual requisition #6216
  • User that are not active doesn't seems to be migrated on omSupply even though they entered historical transactions #6224
  • Type field selector shows empty when importing cold chain equipment #6227
  • Pack Qty shows '0' when multiple batches of the same item get dispensed #6238

[Chris-Petty]

@alainsussol I wonder if there is an easier way to maintain that list of issues found in testing a release? Perhaps a label? If I open an issue while release testing how do you know how to add it here?

[alainsussol]

@Chris-Petty

@alainsussol I wonder if there is an easier way to maintain that list of issues found in testing a release? Perhaps a label? If I open an issue while release testing how do you know how to add it here?

Thanks for the suggestion and I am sure there is an easier way to do this but it is a journey :). Last Release we had issues listed in multiple Release issues with only a link that I had to click on to see the title of the issue and it's status. When you have 50 links or more in a release issue, it takes a long time to go through them before talking to Roxy on release status. So it was what I came up to try to make my life a bit easier :) . I thought that this way I will have all the bugs found by QA during release testing in one place and it is a bit more readable this way as I can see the issue title, the status and if I hover over the link I can see the severity. A bit more practical than last time.

In my mind it was to help me to manage issues opened by QA and I didn't have the intention to list issues found during dev testing or found outside of QA in that list so I didn't think of a way to follow those. But in retrospect, we very probably should list all the bugs found.

I also thought of using a label as it would be easier for everyone to add it but because we need to archive often as we continually reach the project issues limit, I feared to lose some of these labeled issues without realising. But maybe we can use a label in conjunction with an extra column where they are put instead of the done column and reducing the chance that they are archived by mistake ? I am not sure...

I agree that it might be easier to proceed differently if we want to list ALL the issues found during the Release testing. I'll try to improve the process for next release. Keep the suggestions/comments coming though, they are very useful :)

[marthakeezy]

CLOSING DUE TO V2.5.0 BEING RELEASED (but also will continue regression testing)