Skip to content

Latest commit

 

History

History
179 lines (129 loc) · 11.2 KB

File metadata and controls

179 lines (129 loc) · 11.2 KB

CommCare 2.64

Release Notes

What's New

  • [Profile Photo Update] PersonalID users can now update their profile photo directly from the side navigation drawer

Important Bug Fixes

Internal Release Notes

QA Notes

  • PersonalID profile photo update from nav drawer:
    • Sign in to PersonalID and open the side navigation drawer. Verify that the user's image in the drawer header is shown inside a circular white frame with a small camera icon overlay along the bottom edge.
    • Tap the image. Verify that an "Update Profile Photo" confirmation dialog appears with a message asking whether you would like to take a new profile photo, and Continue / Cancel buttons.
    • Verify that the dialog can be dismissed in three ways: tapping Cancel, tapping outside the dialog, and pressing the device back button. In all three cases, the photo should remain unchanged.
    • Tap Continue. Verify that the camera capture screen opens with the title "Take Profile Photo" (it should detect the user's face the same way as during PersonalID signup).
    • Capture a new photo. Verify that the drawer reopens, the new photo replaces the existing image, and the camera icon overlay is still shown along the bottom of the image.
    • Reopen the drawer later (after navigating around the app) and verify that the new photo is still shown.
    • Failed upload: turn on airplane mode, tap the image, and tap the Continue button. Verify that:
      • A toast appears with an error message.
      • The camera overlay icon switches to a yellow warning triangle.
    • With airplane mode still on, navigate around the app and reopen the drawer. Verify that the warning triangle is still shown over the image.
    • Turn airplane mode off, fully close the app (swipe it away from recent apps), and reopen it. Sign back in if needed. Verify that the warning triangle is gone and the camera icon is shown again.
    • With a working network connection, retry the photo update and verify a successful upload restores the camera icon and the new photo persists.
    • Verify that the photo update also reflects on HQ for the PersonalID user (i.e. the new photo is visible on the server-side admin view of the user's profile).

CommCare 2.63

Release Notes

What's New

  • Offline status shown on refreshable Connect pages when applicable

  • Forms now allow a maximum of 50 attachments. To add another after the limit is reached, users will need to remove an existing one first

  • [Relearn Tasking] Added relearn task notification UI to Connect opportunity cards

  • [Relearn Tasking] Implements a new notification when a relearn task is assigned to a user

  • [Work Area Assignment] Implements a new notification when a new work area is assigned to a user

  • [6-box Backup Codes] Using 6-box numeric inputs to collect backup codes from the user

Important Bug Fixes

  • Fixed a crash triggered during combobox item selection when the dropdown list had already been dismissed

Internal Release Notes

  • Session endpoint navigation from Connect notifications: clicking a notification with a session_endpoint_id now navigates the user directly to the specified CommCare session endpoint (after a sync if required), instead of opening the Connect activity.

QA Notes

  • Task and Work Area Assignment Notifications (Connect):

    • On clicking, Notification should take user to the relevant CommCare App Home page and auto-login and auto-syncs the user with a blocking dialog.
    • Click the notification while logged out
    • Click the notification while the app is backgrounded
    • Verify that notifications redirect work as expected from various places in the app - Opp Screen, App Home, Login Screen, Form Entry etc and back navigation works correctly after the notification redirect
    • Verify no regression on existing Connect notification types (payments, messaging, delivery/learn progress).
  • Verify that the existing opportunity card UI is unchanged when there are no relearn tasks.

  • Verify that the opportunity card updates as expected when there are either pending relearn tasks or completed relearn tasks.

  • Verify 6-box input functionality in Backup Code page, including:

    • Showing one or two of the controls depending on recovery/registration mode (respectively)
    • Handling password-style visibility with associated "eye" toggle
    • Verifying matching codes (or error message) in registration mode
    • Text cursor functionality (i.e. backspacing, clicking an earlier box to jump back)
  • Test the new offline status indicator at the top of refreshable Connect pages (Connect Home, Learning Progress, Delivery Progress). Verify that the error message appears when entering these pages while offline, and that it disappears once the device comes back online.

  • Verify that the combobox widget is working as expected when selecting an item that is used to filter another combobox widget and also determines the visibility of some other unrelated question whose relevance condition depends on the selection.

CommCare 2.62

Release Notes

What's New

  • Redesigned Connect landing page for a smoother experience
  • Hausa language support added in Connect and PersonalID
  • Boundary overlays now available on case list maps
  • Unsubscribe from Connect messaging channels
  • Improved payment acknowledgement flow for Connect users
  • Better handling of PersonalID errors on multiple device logins
  • Enhanced GPS accuracy and reliability for GPS capture inside CommCare form

Important Bug Fixes

  • Improved app install reliability on Android 15+
  • Fixed WiFi Direct issue when sharing forms with media
  • Fixed SD card export from forms on Android 15+

QA Notes

  • Run the complete Connect and Personal ID regression plan after updating from CommCare 2.61. It's alright to run a set of regression tests together after updating from 2.61 but we should make sure that each test case is run on an app version that's been updated from 2.61 instead of a fresh install.

  • Connect Upgrade Testing: Do a version upgrade from 2.57.0 to the latest version with a fully set up Personal ID login with opportunities and on upgrade, we should not need to re-login into Personal ID again and should see all the Connect related data as it was before the upgrade, this will need to be tested on all Connect screens.

  • Test manual and automatic GPS capture and verify that the location values are saved correctly inside a CC form.

  • Unsent forms correctly appear on the App Home Screen.

  • Form Entry

    • Test that backing out or completing the form works correctly.
    • Test that form entry with phone rotation is saved and submitted successfully to the server.
    • Test incomplete form save.
  • Login Screen: A video shared here shows steps to reproduce the bug. Verify that it's fixed, and also test various app switching and login scenarios on Login Screen.

  • Changes To Payment Acknowledgement Flow:

  • Verify bug fixes

    • App installs are more reliable on Android 15+ devices.
    • Fixes a Wifi direct bug when sharing forms with media.
    • Fixes SD card export for forms on Android 15+ devices.
  • Connect landing screen redesign changes

    • CCCT-1648: Redesign Connect landing page on the mobile application — Be sure that you are able to see all 3 of the section headers and that they appear correctly in the UI: "In Progress", "New Opportunities", "Completed". Tap on a few opportunities and verify that the expected behavior still happens, especially that you are navigated to the correct app.
    • Already done as part of QA-8382 but QA should do a final check on the release version.
  • Map related changes

    • Earlier QA was done in QA-8273 but QA should run a final check on the release candidate and also tests for the points below.
    • Test the map zooming when entering the Entity Map page, with and without location enabled on the device. Zooming should occur either way.
    • When location is enabled, the user's location should be factored into the zoom calculation so the user is included.
    • Rerun the performance testing done in QA-8273 and document the limits.
  • Hausa translation: No need for detailed testing on this but do a smoke test going over different Connect Screens to see if anything looks weird.

  • PersonalID improvement for multiple device login

    • Login to a PersonalID account that is currently logged in on a different device and has recently been accessed.
    • Verify that on successful login the new device shows the notification indicating that the old device was logged out.
    • Steps for triggering the lost config while in form entry:
      1. While on the Login page, turn on airplane mode.
      2. Login to a Connect app and enter form delivery.
      3. Turn off airplane mode and wait a few seconds for a background network request to attempt and fail (there should be no visible activity to the user, the call happens under the hood).
      4. Leave form entry, try to Sync on the home page, and verify the app bumps out to Login page and shows the error message.
    • Note that PersonalID tokens last 10 hours, and are not invalidated when a new login occurs. So after logging in on a second device, you will need to wait 10 hours before attempting to use the first device again (in order to trigger the error).
  • Push notification related changes — user receives push notification whenever:

  • Messaging channel subscription: Test Subscribe and Unsubscribe for Connect messaging channels; unsubscribed channels should not receive any messages.