3.6.0 Release Candidate is Out – Join Us for QA Testing!

Community
1

:tada: Release Candidate is Out - Join Us for QA Testing!

We’re thrilled to announce that the Release Candidate is now available, and Test3 is ready for QA testing!

This milestone wouldn’t have been possible without the incredible dedication of all our contributors — and a special heartfelt thank you to Ian, Daniel, and Dennis for working tirelessly behind the scenes to get us here. :folded_hands:

:waving_hand: We Want YOU to Participate!

We’re inviting community members to join us in testing the Release Candidate. Whether you’re a seasoned tester or trying QA for the first time, your contribution matters — every bug found now is a problem avoided in production.

Here’s what you’ll need to get started:

:clipboard: QA Testing Checklist

:open_book: Guide for Manual QA Testing

Please drop a comment below if you’re joining the testing effort or if you have any questions. Let’s work together to ship a solid release! :rocket:

Happy testing, everyone!

6 Likes
2

Is this a known issue,

when registering a patient, having filled in their name, Sex, Age and D.O.B, i try searching for an address, when i search for an address(even with a non existent address) and hit enter, the patient is registered immediately without me hitting the registration button

3

“Hi @tendomart and everyone! I’m joining the testing effort for the Release Candidate. I’ve been working on automation testing with Selenium and Java, and I’d love to help verify the patient registration bug mentioned here. I’ll start by following the Manual QA Guide and the Checklist provided. Happy to contribute to a solid release!”

1 Like
4

I guess this is the same question in Slack with the responses.

5

Yes , i created a Ticket at O3-5465

1 Like
6

Hello Community

I recently completed manual QA testing of the latest Release Candidate on test3.openmrs.org using the mobile view. My testing mainly focused on patient registration, vitals recording, and form entry.

Testing details:

  • Environment: test3.openmrs.org (mobile view)
  • Credentials used: admin / Admin123
  • Total test cases executed: 24
  • Result: 23 passed, 1 issue observed

Observations during testing:

  • Patient registration worked smoothly and the OpenMRS ID was generated instantly.
  • The demographic information entered during registration (name, gender, age) appeared correctly in the patient chart header.
  • Recording vitals such as temperature, blood pressure, and SpO₂ worked as expected.
  • Visit Notes and AMPATH forms were saved and edited successfully without issues.

Issue noticed: While testing the Vitals form, I observed that some required fields do not immediately show a validation message when left empty. This might make it slightly unclear for users while submitting the form. Test Case Automation for OpenMRS.pdf (18.2 KB)

I have documented the test cases and results in an Excel sheet.

I am also starting to automate some of these scenarios using Selenium with Java and Cucumber to build a small regression suite for these workflows.

Please let me know if there are other areas where I can help with testing. I’m happy to continue contributing.

Best regards, Vishnu Vardhan

7

@vishnu_vardhan, Thanks so much for your contributions to the QA exercise — it’s really appreciated! I’ve attached two documents that can guide you on additional areas to explore. Please have a look and don’t hesitate to reach out if you have any questions.

  1. O3 QA & Clinical Release Checklist - Google Drive
  2. A Step-By-Step Manual QA Guide for OpenMRS - Google Docs
1 Like
8

Thank you so much for sharing these documents! I have read through the O3 QA Checklist and the Manual QA Guide carefully. I have started going through the testing steps on the O3 demo at o3.openmrs.org.

9

Hi [Mentor],

I have completed manual testing for the “Clinical Release Checklist” on the O3 environment and have identified two critical safety-related bugs:

  1. Drug-Allergy Interaction: The system allowed me to sign a medication order (Aspirin) despite a recorded “Severe” allergy.
  2. Dosage Validation: The system accepted an extreme dose (10,000mg) without any warning or boundary validation.

I have verified these as known gaps in the current build. I am now working on converting these manual test cases into Playwright scripts to ensure these clinical safety points are covered in our automated regression suite.

I’ll share the scripts once they are ready for review. Best regards, Vishnu Vardhan P.

10

Hi Mentor

I have been working through the OpenMRS O3 Manual QA & Clinical Release Checklist to better understand the system workflows. To support the community’s quality assurance efforts, I have successfully automated 15+ test cases from the checklist using Playwright and TypeScript.

Github Repository: GitHub - Vardhan466/OpenMRS-Checklist · GitHub

Key Highlights:

Test Coverage: Automated flows for Patient Registration, Vitals, Medications, Lab Orders, and Conditions. Bug Verification: My scripts have successfully reproduced and documented several known issues, specifically:

  • TC_REG_005 (Duplicate Patient): Verified current behavior during registration.
  • TC_CON_006 (Duplicate Condition): Confirmed Bug O3-5444. The system currently allows saving duplicate conditions (e.g., Malaria) without the expected warning.
  • Clinical Safety: Confirmed missing alerts for drug-allergy interactions and out-of-range dosages (10,000mg).

Framework Features:

  • Implemented a global-setup for efficient authentication.
  • Structured the project with reusable fixtures for cleaner test scripts.

I would appreciate any feedback from the QA team or mentors on these scripts as I continue to expand the coverage.

Best regards,

Vishnu Vardhan P.

11

I have finalized my GSoC 2026 proposal based on my work with the Playwright framework and the O3 checklist. You can view my draft here: VishnuVardhan - OpenMRS_GSoC_2026_Proposal.pdf (186.3 KB)]. I would appreciate any final feedback from the mentors!