How-to: Integrate Community QA Processes and Tools into the Development Process


The purpose of this protocol is to guide teams and squads on successfully integrating OpenMRS community QA processes and tools into a development cycle. This includes:

  • Reviewing and assessing available community QA processes and tools
  • Prioritizing test cases for automation
  • Creating a QA plan that includes selected QA processes and tools
  • Building your team’s QA awareness, skills, and knowledge
  • Reviewing QA results 
Review and assess available community QA processes and tools

Step 1: Conduct an initial meeting with the QA Support Team to discuss your project’s QA needs, current practices, and timelines

Step 2: Review available community QA process and tools (demos)

Step 3: Select an automated test framework (if applicable). The Reference Application uses Selenium.

Prioritize test cases for automation

Step 1: Review the QA Test Case Roadmap 

Step 2: Make a copy of the QA Prioritization spreadsheet to use for prioritizing test cases for automation

Create a QA plan

Step 1: Create a Test plan.

Step 2: Review the test plan with your team and the QA team.

Step 3: Use the test plan to guide the testing process.

Build your team’s QA capacity

Step 1: Schedule a working session with the QA Support Team.

Step 2: Review of QA Framework Technical Documentation and a quick guide on how to use CucumberStudio.

Step 3: Set up your QA environment

Step 4: Develop prioritized test cases using your automated framework and CucumberStudio

Trial a sub-set of test cases  

Step 1: Run 2-3 test cases using CucumberStudio

Step 2: Identify improvements to make to test cases based on results.

Step 3: Share results with the development team. 

Step 4: Decide to proceed with automated testing for the release.