Create a generic ObsToObsFlowSheet similar to ObsDisplayControl. The ObsToObsFlowSheet looks like this

This class should accept WebElement as a constructor. It should expose the below methods

Map<String, List<String>> getValues(){} - The key is the header column name and the List<String> are the values.

The spec step should take the structure similar to what we see on the UI.

Context

Automate the creation of a baseline form for a patient through the UI.

Add a generic test step for ObsDisplayControl. It should be generic for Bahmni

This test case should test the role-based access for Bahmni. The following needs to be verified

1. A user with Read-Only access should not be able to save data in Bahmni
2. A user with Registration access should not access any other apps

ReadMe shouldn't have endtb specific configurations to run specs. The respective implementation folders can have this details.

The StringUtils.setDateTime() method as it is copied and pasted in BaseSpec instead of using it from StringUtils? Please do refactoring around this so that we knowingly introduce the duplicate code.

We should be able to support inactivating the patients as part of TearDown step.

• Create a method called retirePatient() in BahmniRestClient. A REST call should be made to retire the patient by identifier.
• Create a step in RegistrationFirstPageSpec which takes the patient detail from the DataStore and invokes the above method
• Add this step in all the existing test specs

The Bacteriology Results Control looks like this. Create support for it bahmni-gauge-commons like this ObsDisplayControl

This class should accept WebElement as a constructor. It should expose the below methods

Map<String, String> getValues(String resultName){} - The key is the header column name and the String are the values. The resultName denotes the various results like Smear Microscopy Test Results, Xpert Test Results

We should not be putting passwords in plain text in the specs as we check-in the files to the github. We should store these passwords either as CSV file (managed internally in an environment without checking-in) or as environment variables (manage as secure variables in gocd).

Steps like this should be avoided - Login with username "superman" and password "Admin12345"

Context

To test some display controls on the patient dashboard, its often handy to save the form using an API. It saves time for test execution as well.

Create a gauge step for creating any form using REST Services

Tech Tasks

• Every implementation will be creating an object for each form. For e.g. BaselineForm of endtb will have a class defined. These class should extend BahmniForm
• Create a method in BahmniRestClient with the below signature. The ftlTemplateName is driven through the implementation specific freemarker templates of JSON.

void saveObservationForm(String ftlTemplateName, BahmniForm form)

• Write a step in ObservationPageSpec called

  create the form using api

The ObsDisplayControl is currently created for endTB. It needs to be generalized for the product.

• Create Scenarios around Editing of the Program Enrollment
• Create Scenarios around Deleting of the Program Enrollment
• Extend the spec "enrollPatientsToProgram" to have additional scenarios

After running the instructions given in this repo : https://github.com/Bahmni/bahmni-gauge all tests fails 😦 I've been trying all day long but it keeps appearing the same error message. The error start since the first login step : Error Message: java.lang.ExceptionInInitializerError

I've been investigating and that error is due to a wrong initialization in a static variable.
Can anyone help me with this please ?.

The drug-order-details display control looks like this.

Create support for it bahmni-gauge-commons like this ObsDisplayControl

This class should accept WebElement as a constructor. It should expose the below methods

Map<String, List<String>> getValues(){} - The key is the header column name and the List<String> are the values.

• Create a REST Api
• Provide Program attributes from the spec table

WaitForElement needs refactoring in order to define better synchronization across pages

The Drug-O-Gram looks like this. Create support for it bahmni-gauge-commons like this ObsDisplayControl

This class should accept WebElement as a constructor. It should expose the below methods

Map<String, List<String>> getValues(){} - The key is the header column name and the List<String> are the values.

Add support for adding multiple Drugs in one API call

1. Create a class called DrugOrder. This class should support all the fields that are accepted by UI.
2. Add the below method in BahmniRestClient
   createDrugOrders(List<DrugOrder> drugOrders) - Creates the drug orders using EMRAPI
3. The spec should accept a table containing various fields required for creation of drug order. This table should be able to accept multiple drug orders (i.e. multiple rows should be supported in the table).

Add support for adding bacteriology sample using API.

1. Create a class called Specimen. This class should support all the fields that are accepted by UI for creating a specimen.
2. Add the below method in BahmniRestClient createBacteriologySpecimen(Specimen specimen) - Creates the Bacteriology sample using EMRAPI
3. The spec should accept a table containing various fields required for creation of sample. This table should be able to accept multiple Samples (i.e. multiple rows should be supported in the table).

Support for sanity tests in various environments. Add the sanity tag to these testcases so that it can be run on multiple environments

• Ensure that msfuser1 is existing on the environment
• Ensure that pihuser1 is existing on the environment
• Ensure that irduser1 is existing on the environment

This story is linked to 17.

1. The DrugOrder class created in issue 17 should be used to fill up the Treatment tab.
2. Create TreatmentPage class. Add a method called createDrugOrder() to create a drug order
3. Add TreatmentPageSpec class. This class should contain steps to accept a Table of DrugOrder.

The Forms Edit Display Control looks like this. Create support for it bahmni-gauge-commons like this ObsDisplayControl

This class should accept WebElement as a constructor. It should expose the below methods

List getValues(){} - Returns the list of forms that are configured on the display control.

Future enhancements could be based on the edit part of the display control. It is out of scope for this card.