Hello everyone:
The QA support team has been working on adding automation tests and also resurrecting previous automated tests to increase the test coverage in our releases. Those who have had a look at the existing tests may have noted that the tests are granular like adding an appointment, deleting an appointment, adding a service type e.t.c. While this is very useful in ensuring that the system is thoroughly tested from a technical point of view, most of our implementers/community members may not have a clear understanding of what is working and not working on a high level. With this in mind, the QA support team would like to adopt workflow-based testing.
Workflow-based testing involves writing test cases that mimic the user experience in a live environment. In developing these tests, there are 3 approaches envisioned. We would like to hear from you as an Implementer/ community member on what approach would help you understand and confidently support that the OpenMRS Reference application has been well tested and ready for use.
Additionally, here is a link to a document where we have listed some of the most common workflows based on various user roles.
Below are three approaches and representation of how the test results would be displayed on a dashboard:
Big-Workflow Based
- Outpatient Clinic Workflow
- Inpatient Ward Workflow
Persona Based
- Registration Clerk
- Triage Nurse
- Doctor
- Data Clerk
- Admin
Goal Based
- Search & Registration
- Vitals & Triaging
- Clinical Visit
- Report Generation
- User Creation
- Big-Workflow Based
- Persona Based
- Goal Based
0 voters
@grace @janflowers @jennifer @luciekimotho @ssmusoke @eddiemu @ddesimone @burke @k.joseph @dkayiwa @herbert24 @gracebish @tendomart @irenyak1 @kdaud @sharif