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

Kiribati: Upgrade testing #5296

Open
AnushaUp opened this issue Aug 21, 2023 · 6 comments
Open

Kiribati: Upgrade testing #5296

AnushaUp opened this issue Aug 21, 2023 · 6 comments

Comments

@AnushaUp
Copy link

AnushaUp commented Aug 21, 2023

Describe the bug

Client Upgrade testing for Kiribati vax. Kiribati and vaccination related issues will be addressed here and upgrade process will be done taking the client data in local server.

Issues included in testing are :-

  1. General Sync.
  2. When searching online for a patient, duplicate patient alert is triggered when patient is selected #5241
  3. Set some more fields as mandatory #5239
  4. case sensitive should not be checked during creating name #5237
  5. Patient > DoB > Allow a valid date entry by typing #5157

Version and device info

  • Server is on v603 should be upgraded to latest version 707.
  • App version: [v8.6.1 - present version ] to be upgraded to [v6.6.7]
  • Tablet model:
  • OS version:

Moneyworks jobcode

@AnushaUp AnushaUp added Bug: ???? Placeholder; replace with 'development' or 'production' Upgrade Testing tester: Anusha 8.6.1 8.6.7 and removed Bug: ???? Placeholder; replace with 'development' or 'production' labels Aug 21, 2023
@AnushaUp
Copy link
Author

AnushaUp commented Aug 23, 2023

The initialisation and setup process for kiribati datafile was extremely slow and took 5 days just for the setup to be completed since the process is stuck in between from time to time and have to restart app and set the credentials again and again.
Maybe due to the process being so lengthy there's problem with the visibility of items and existing items were not visible in the particular store of mobile.
Issue made HERE

@AnushaUp
Copy link
Author

ALL RECORDS([item])
QUERY([item]; [item]type_of="general")

While (Not(End selection([item])))
QUERY([item_store_join]; [item_store_join]item_ID=[item]ID)
QUERY SELECTION([item_store_join]; [item_store_join]store_ID=<>t_current_store_ID)

If (Records in selection([item_store_join])=0)
CREATE RECORD([item_store_join])
[item_store_join]ID:=UUID_generate
[item_store_join]item_ID:=[item]ID
[item_store_join]store_ID:=<>t_current_store_ID
[item_store_join]inactive:=False
[item_store_join]pack_to_one:=True
[item_store_join]pack_to_one_allow:=True
[item_store_join]restricted_location_type_id:=[item]restricted_location_type_ID
[item_store_join]forecast_method:=1
SAVE RECORD([item_store_join])
Else
If (pm_load_record(->[item_store_join]))
[item_store_join]inactive:=False
SAVE RECORD([item_store_join])
End if
End if
pm_unload_record(->[item_store_join])
sync_create_syncout_record_UUID(Table(->[item_store_join]); "U"; [item_store_join]ID; 1; [item_store_join]store_ID)
NEXT RECORD([item])
End while

@anildahalsussol wrote this code for visibility of items.

@AnushaUp
Copy link
Author

While setting up site for the new site without the syncMonths value the setup was completed within 1 and half day in v8.6.1 so I suppose there's some problem in the syncMoths. And also the above mentioned issue was also seen in the site setup with syncMonths field. So there's no any problem as mentioned above.
But there are some other problems which are seen on new site and they are:

  1. Prescriber list is seen blank.
    photo_2023-08-29 12 20 38 pm
  2. Ci is created with the same invoice number
    photo_2023-08-29 12 23 30 pm

@AnushaUp
Copy link
Author

As per the discussion with @arjunSussol dai we will first update the mobile version and perform the regression test and also make sure the above issue is fixed otherwise have to make issue if seen on latest.

@AnushaUp
Copy link
Author

The above issues which were found in the previous version were not recreated so didn't make issues
All the issues are tested and passed but this one issue is remaining in the vaccine #5271 which is still there and others looks fine.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant