...
Overall Goal: Set up tests that automate realistic User Workflows for openrms-esm-patient-chart and openmrs-esm-core and show the squad the results, with a warning indicator on a shared Repo ReadMe so that no one misses failing tests.
- The smoke tests are organized according to user workflows, reflecting a user’s perspective.
- A limited number of E2E tests are performed on the happy-path user stories (when everything goes smoothly).
- These tests do not cover every possible interaction or scenario. Detailed functional tests, which are beyond the scope of this E2E Workflow-based draft, are responsible for that.
- Consider the transitions between different parts of the application, managed by different Microfrontends, when developing these tests.
- Our goal is for business-level users to easily understand the extent of functionality coverage through reports like this, and to quickly identify areas that may need improvement.
Documentation
Detailed Project Report
Weekly Reports
Issues
Issue Number | Issue Link | Pull Request | Status | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| O3-2106 |
| Set up patient chart repo for e2e testing | TO DO | ||||||||
| O3-2107 |
| Write E2E tests for record allergies | TO DO | ||||||||
| O3-2108 |
| Write E2E test to add medication and delete medication - Patient Chart | TO DO | ||||||||
| O3-2109 |
| Write E2E test for add vitals and biometrics - Patient Chart | TO DO | ||||||||
| O3-2110 |
| Write E2E tests for add, edit, and delete conditions - Patient chart | TO DO | ||||||||
| O3-2111 |
| Write an E2E test to add a program - Patient Chart | TO DO | ||||||||
| O3-2112 |
| Write an E2E test to add notes - Patient chart | TO DO | ||||||||
| O3-2113 |
| Setup the Core repository for E2E testing | TO DO | ||||||||
| O3-2114 |
| Write an E2E test to login and log out - Core | TO DO |
Medium Articles
Meeting Notes
Final Presentation
...