Changes to OpenMRS QA Structure

Dear OpenMRS Community,

I hope this message finds you well. We’re reaching out today to inform you of some changes happening within our community.

After careful consideration and in response to the evolving needs of our project, we’ve decided to integrate the Quality Assurance (QA) efforts more seamlessly into our development process. As a result, we will be phasing out the weekly QA call that traditionally took place on Tuesdays.

What does this mean for you?

No More Weekly QA Call: The weekly QA call on Tuesdays will no longer be held, starting 2023-11-20T18:30:00Z.

QA Support Channel: For any questions or assistance related to QA, we encourage you to use the :speech_balloon: #qa-support-team :speech_balloon: channel on Slack. This channel will serve as a hub for QA discussions and support.

Other Communication Channels: Remember, we have various communication methods available, including daily coffee break calls, OpenMRS Talk and other avenues. Feel free to leverage these platforms for any QA-related inquiries. Call times and Zoom links can be found on the Community Calendar here: :spiral_calendar: :spiral_calendar:

Why are we making this change?

Our goal is to foster a more collaborative and integrated development environment. By eliminating the distinction between the QA team and development, we aim to streamline our processes and enhance communication within the community. This change aligns with our commitment to continuous improvement and efficiency.

Your Feedback Matters:

We value your input, and we want to ensure that this transition is as smooth as possible. If you have any thoughts, concerns, or suggestions, please don’t hesitate to share them with us. Your feedback is essential in shaping the future of OpenMRS.

Thank you for your continued dedication to the OpenMRS community. We look forward to this new chapter and the positive impact it will have on our collaborative efforts.

cc: @ayushmishra @piumal1999 @anjisvj @randila @grace @christine @ibacher @dennis @dkayiwa


I love the direction of baking QA into all our development expectations!

@dkigen let’s make sure to remember - especially in these next few weeks - to ask regularly on the O3 Squad calls if anyone has any questions about Playwright test-writing, or any other test-related questions.

In the meantime:

@jayasanka can you please create some tickets to cover any other automated tests we should have in O3?

And can you share the link to the Epic for that, here?

And, are there any other Epics/Tickets for other types of automated tests that should be set up - e.g. known gaps in integration test or unit test coverage?

Sure. I’ll get back to you.

1 Like