A new QA Team in OpenMRS!

The OpenMRS QA team is a new group that aims to establish a systematic quality assurance process for OpenMRS software products. The initial team formation and the first year’s scope for the team is graciously funded by Digital Square Notice C, and is tasked to set up a community acceptable automated end-to-end testing framework and tools which is community sustainable and will improve the overall quality of OpenMRS products.

Don’t We Already Do QA? Moving Us from Reactive to Proactive Quality Assurance

The QA team’s mission is to ensure the community release of quality OpenMRS software. We aim to achieve that mission by improving upon the current QA activities, which aim at finding bugs, to establish a proactive and systematic QA process within the community aimed at preventing bugs. This includes improving the overall QA process itself, the adoption of an automated test framework and tools, and the inclusion of implementers and stakeholders in the testing of our products. We aim to create the QA process so that it is adaptable to ensure continued use and implementation beyond our startup funding. The QA team has four major areas for the startup year:

The team’s goals are as follows:

  1. Community-led.
  2. Sustainable and robust testing processes and framework.
  3. Foster a culture of quality assurance in developer and implementer practices.
  4. To produce high-quality OpenMRS products.

The team’s approach to establishing for this first year are to:

  1. Develop a portfolio of documented manual test scripts and anonymous data sets for testing the suite of OpenMRS products.
  2. Develop an automated End to End testing framework.
  3. Create and publish SOP for Implementer Acceptance Testing for software releases.
  4. A pilot test framework with OpenMRS release, and pilot SOP of implementer acceptance testing.

The OpenMRS QA Team

We are eager to engage any community member interested in joining the mission and leading various tasks to improve the QA program for OpenMRS.

These community members will be leading the initial QA team during this startup period:

  1. @christine , QA Technical Project Manager (TPM).
  2. @ivanc , QA Test Engineer.
  3. QA Test Engineer(To be shared soon).
  4. @janflowers and @jennifer, Management and Grant oversight.

Communication channels and information access

  1. Slack: https://slack.openmrs.org/ channel #qa_team
  2. Wiki: https://wiki.openmrs.org/pages/viewpage.action?pageId=229442591
  3. Talk: QA category
  4. Documentation: https://drive.google.com/open?id=1JGv03ZqXY8C-nFkzbhllwCov4y7_d7vA
  5. Team Meeting Time: Tuesday 10:30pm IST | 8pm EAT | 7pm Cape Town | 5pm Accra | 12 noon Boston | 9am Seattle. To join the call by phone, dial +1-888-510-4073. To join the call using Audio, Chat, & Screen Sharing please use a compatible browser (Chrome, Firefox, Edge) and go to: http://www.uberconference.com/openmrs

It will be great working with the new team so as to improve the QA process

1 Like

Great Strides!, So awesome to see this coming to life.

1 Like

Woow , we are glad to have this innitiative in openmrs ,and i believe t will be great working with the QA team with you @christine as the Lead.

Am also highly intrested in joining the mission :slightly_smiling_face:


@Congratulations team and all the best on your endeavors!


Great to see this.

Hi @christine That URL is private, is that what you want?
Due to the nature of our work, I assume you either want to make that document public or be part of our wiki,

Hey @cintiadr, I have changed rights to the folder. Now anyone who click on the folder should be able to view the contents of the folder.

8 posts were split to a new topic: Tools for testing OpenMRS implementation