Hope you found the previous webinar on CHT test harness informative and valuable. Unfortunately we could not cover everything we planned for last time. But guess what? We are having a second webinar on CHT test harness on Thursday, July 25th 2024 at 4:00 pm EAT/1:00 pm GMT/6:45 pm NPT. We will be covering more test case scenarios along with a demo. Please join us to learn more on testing your CHT application configuration along with some best practices we recommend.
Thank you to those who attended the second webinar on CHT Test Harness. We hope that you found the webinar informative and valuable. You can find the recording here and below is the summary of what we covered during the webinar.
Contact summary
In this section, @paulalogno showed how to test contact summary. Contact summaries display basic information about the contact. Contact summary displays information about a person’s patient id, age, sex, phone number, and information about the place they belong to. Each field that can be shown on a contact’s profile is defined as an object in the fields array of contact-summary.templated.js. The properties for each object determine how and when the field is shown. You can watch Paul showing how to test contact summary using getContactSummary().
Test workflow with hierarchy
@kembo explains how they overcame challenges testing with multiple hierarchies. Brink developed a disease surveillance app with 3 levels of hierarchy i.e. CHP, CHA and a disease surveillance officer (DSO). In the app, testing tasks and targets for all three of them became challenging as multiple .default.json files were created for CHA and DSOs. The problem with having multiple files is that it is repetitive and may not be a best practice. In this webinar, @kembo walked through the solution of having one defaults.harness.json file.
Cron Job and batch processing
We may have workflows that need to be processed over and over again at regular intervals of time. For example, pregnancy home visit service, which is typical for most ANC types of visit that are scheduled for pregnant women. While most commonly a technical person tests the application, a better approach is to have a non-technical people run the tests too. @elijah showed an approach in which a spreadsheet can be used to map different test conditions such that it can be be run by non-technical team members in the project. Please stay tuned for a working example of this in a CHT app.
Best practices
@elijah shared some of the best practices on testing CHT applications. It is important to think about edge cases when you design test automation. Also, the other way to make your CHT app robust is to have early and frequent testing. Also, collective ownership of tests makes sure that all the development team members are aware of what it means to write tests. Furthermore, the early approach was to have one or two people for testing while others develop the application. But the recommended approach is that all developers have the ability to write test cases and test the part they are working on. Also, it is important to prioritize detailed & quality test reporting. Here are various tools available that can produce coverage reports which may be helpful for your app testing.
Thanks again for your participation and we look forward to seeing you in future CHT webinars.
,
.
and below is the summary of what we covered during the webinar.