# QA for O3 + OHRI: Summary of main current qa initiatives

**URL:** <https://talk.openmrs.org/t/qa-for-o3-ohri-summary-of-main-current-qa-initiatives/37122>\
**Category:** Quality Assurance\
**Tags:** qaframework, 3x, qa, ohri, o3\
**Created:** [July 22, 2022, 1:01am UTC](https://talk.openmrs.org/t/qa-for-o3-ohri-summary-of-main-current-qa-initiatives/37122 "2022-07-22T01:01:46Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![grace](https://talk.openmrs.org/user_avatar/talk.openmrs.org/grace/32/16942_2.png) [@grace](https://talk.openmrs.org/u/grace)\
**Post date:** [July 22, 2022, 1:12am UTC](https://talk.openmrs.org/t/qa-for-o3-ohri-summary-of-main-current-qa-initiatives/37122/2 "2022-07-22T01:12:00Z")

</div>

# OHRI-Specific

### OHRI: Setup E2E Automated Tests

We have found the E2E UI-based automated tests have indeed already paid off for us in OpenMRS([Recent QA Automation Success Story!](https://talk.openmrs.org/t/recent-qa-automation-success-story/37064)), and the OHRI team is interested too. The OpenMRS BDD-based Frontend Test Framework can be leveraged for this purpose, and some cypress tests already written for O3 may be useful for the OHRI package. We will try 2-3 simple happy-path E2E tests for major OHRI functionalities. We could start by focusing on items that OHRI devs tend to touch in their day-to-day work. Next steps TBC with @eudson & @christine, and I believe @larslemos has been doing some smoke tests for OHRI environments.

### O3 + OHRI: Finding out what happens when we combine them

- Goal: A distro of OpenMRS should be able to add an OHRI package without their O3 apps being adversely affected.
- Problem: Manual testing of the OHRI package had been focused on an environment where the OHRI package itself was the only EMR functionality.
- Plan: Thanks to support from @alaboso, @ibacher, and @eudson, the representative “combo” testing environment was set up at [ohri.o3.openmrs.org](http://ohri.o3.openmrs.org). Recently @christine (OMRS) and Veronica Muthee (UCSF) worked together to manually test the look, feel, and workflows in this combo setting. You can see a triaged inventory of the \*\*[issues identified in their manual QA review here](https://docs.google.com/spreadsheets/d/1dfsKSK5IhffZxbZBu07oHVkSesXvyvKJtFFO1mF8u2w/edit#gid=0). They also cross-checked if the identified issues exist in the separate OHRI demo vs O3 dev environments. Next they are logging known bugs into the relevant Jiras (eg OHRI vs OpenMRS).

---

_[View the full topic](https://talk.openmrs.org/t/qa-for-o3-ohri-summary-of-main-current-qa-initiatives/37122)._