Test Coverage for our REST API

[kdaud (Kakumirizi Daud)]

@grace

• Historically, doing manual tests of our REST API delays our Platform releases (example of manual tests here ).
• There are some existing REST WS tests, like these (which are buried and hard to find), but it’s not clear how much coverage our REST API has.

I haven’t studied this in too much detail when it comes to REST API tests, one thing I would like to know is whether there is any automated tests(testing) for the module ?

@grace

Given that our REST API is something ALL OpenMRS system users leverage, we should feel confident in our coverage of REST WS.

This suggests to me setting up automated configuration within the module and have automated tests written especially for critical functionalities. @ibacher @dkayiwa @sharif @bistenes @mksd does Selenium or Cypress apply in this case? If yes, which one would be more useful to achieve the goal in a more light-weight way?

@grace

• First: Platform Team Members (e.g. @dkayiwa, others?) to take a dozen of these tests, i.d. most critical ones, cross-check that these exist in the existing RESTWS tests. Then, create tickets for those that are left out and still need to be added in to the RESTWS module.
• Then: QA Support Team Members can write tests for those that are missing

@grace @dkayiwa would be a good idea to have these tickets on our QA-Kanban-Board distinctively labelled for members to pick them up and work on them.