We need that for UI tests to be executed more reliably. Our tests misbehaved and broke those instances a few times last week. We need an automatic way to recover to a healthy state after fixing tests.
Is there a possibility of an to manually reset the database on devtest01 as an incomplete deletion of created patients in UI Tests causes existence of active visits of deleted patients that break visit and patient UI Tests.
I’m not particularly sure. I don’t think I do have access to the repository
where they belong.
So the demo server apparently has a lot of scripts (
https://ci.openmrs.org/browse/RELEASE-RTMGIT-TE-43/log), I guess they got
there using Ansible, puppet or anything, but I don’t know why devtest01
server doesn’t have it:
Yes, they were written for the demo server so that is the only server that has them. I can deploy them to the same location on each of the devtest servers. I will also add the scripts to the ITSM repo.
I have deployed the dbreset scripts out to /opt/scripts/dbreset on the devtest hosts. You will need to create a .my.cnf file with the appropriate data before running the demo_db_reload.sh script. You can use .my.cnf.example in the same dir as a template. Let me know if any other hosts need this and I will add them to the list.