QA testing for 3.8.0-rc.2 on test3

Community
, ,
1

Hi everyone,

Thanks to everyone who tested rc.1. You found a set of regressions and rough edges, and it was a fairly small list, which is a good sign for this release. They’ve all been fixed and tracked here: 3.8.0 Release Candidate Bugs

We’ve rolled those fixes into 3.8.0-rc.2, which is now up on test3.openmrs.org. Please give it another round, focusing on the areas below. Each ticket has steps to reproduce, so you can check the original problem is gone.

What to retest

  • Lab orders: Modify a lab order from the patient chart (for example, change Routine to Stat). It should still show up in the Laboratory app with the new priority. O3-6095

  • Patient lists: From a patient’s chart, go to Add to list → Create new patient list. You should land back in the Add to list form with the new list ticked, ready to save. O3-6096

  • Drug orders: The “Free text dosage” toggle label should match its actual state (Off when off, On when on). O3-6097

  • Service Queues: Expand a patient row. “Scheduled for today” and “On time” shouldn’t appear when there’s no data behind them. O3-6098

  • Vitals: Double-click Save and close on a slow connection. Only one vitals entry should be saved. O3-6100

  • Tablet layout: At tablet width, the Appointments, Service Queues, and Stock Management dashboards should fit the screen with no buttons cut off at the right edge. O3-6106

  • Forms: A few form engine fixes also went in:

    • Datetime fields no longer shift by a day across timezones. O3-5847
    • Editing a form no longer creates duplicate obs for values you didn’t change. (commit)
    • Checkbox groups now show their validation errors. (commit)
    • Post-submission actions were reworked. (commit)

    For forms, fill in, save, and edit forms that have datetime fields, checkbox groups, and post-submission actions. Then check the saved values look right.

Everything from the rc.1 post still applies. If you didn’t get to the new features last time, now’s a good time.

Found something? Same as before: file it in Jira with steps to reproduce, and tag it 3.8.0-rc.2. If you’re not sure whether it’s a bug, post it here.

Thanks again, everyone. We’re getting close :heart:

1 Like