One of our key tech strategies at the moment is test automation (i.e. to increase trust & qa in OMRS tooling). Are there 1-2 tangibly useful things, such as integration or lint coverage, that we should add to this 2.5 plan? Half of the issues below are in-progress, so why not add them to our Platform Release to increase awareness of the automation work we are doing to increase resiliency and trust in the Platform?
Here are some ideas based on recent discussion in the QA Support Team:
Platform Tests should show up on our QA Dashboard, e.g. should be easy for an implementer to see on our Dashboard that PostgreSQL, MySQL, MariaDB, and the Wizard are all passing with the latest builds
Thanks @grace for bringing this up . Let’s wait and see what others think .Did you manage to get any feedback from the MF Squad concerning user_patient_property ?
I don’t think we need that ticket per-se. We already have some of those tests in the QA Dashboard. See here.
What we might want are RefApp tests against those databases.
We have tests for PostgreSQL and MySQL. We could add a similar flow for MariaDB. I’m not sure what “the Wizard” is in this sense since all of those test flows are going to need to run through the install wizard, so it’s not really a separately testable item.
I’d like to see greater Sonar adoption for more than just core too, but we should maybe things about migrating things to Sonar Cloud, especially for PR adoption. Sonar is one of those things that runs on OpenMRS’s infrastructure but isn’t kept up-to-date (we’re on a release from 2017). Sonar Cloud claims to be free for public projects.