Info |
---|
Bahmni QA & Automation Testing related artefacts |
...
Scenarios covered under E2E tests
https://github.com/Bahmni/bahmni-e2e-tests.git has smoke workflows of Bahmni End to End tests. The Github actions are configured to run these tests. The results can be viewed at https://github.com/Bahmni/bahmni-e2e-tests/actions
Module | Scenarios |
---|---|
| Note:- Covered as a part of other E2E scenarios
|
|
|
|
|
|
|
| Note:- Covered as a part of other E2E scenarios
|
| Note:- Covered as a part of other E2E scenarios
|
|
|
|
|
|
|
| Development is complete but not used in the workflow. Using InPatient Module instead. |
| Covered as a part of Clinical module test case |
| ODOO automation done not running because of the sync issue. |
Scenarios yet to be automated
Module | Scenario |
---|---|
| Form builder |
| |
| Manage beds Order set Concept Dictionary create report To do list scenarios under Administration |
| We will need to create a Bahmni-PACS-simulator image based on the steps mentioned in Test PACS Setup with Bahmni PACS Simulator . We should create a node library that will listen to an endpoint that should be deployed only on the QA Bahmni setup. When that end point is hit with parameters of patient's name and other details it has to run the command to return the image. |
| Recurring appointments Tele-consultation |