Week 05: GSoC 2022 with OpenMRS
Coding Period Week 05
Hello Everyone.
It is the fifth week of the coding period in Gsoc:2022. In the previous week, I had to clear up the new repository by removing unwanted files, and folders in it. And also I changed the path of the integration folder to take the features file to a simple folder path. You can read the past week’s blog post here. In this blog post, I’ll be sharing the experience of the fifth week in Gsoc:2022.
As I mentioned above now we have a clean repository for the 3.x E2E testing. The next step will be to fix the existing test scenarios. So for that purpose, I have support from the Quality assurance team as well. And my next task was to fix the data mutation issue that occurs with the test scenarios. Jira ticket number: O3–1316. From here, I will demonstrate the implementation of the solution for the data mutation issue.
The proposed solution for the issue: Gsoc proposal: Implementation of the solution for the data mutation issue.
Basically, the implementation is included with,
- Script files for the following purposes.
1. Take a Dump File of a database.
2. Restore the database. - npm commands to run the following scripts.
By implementing these things I have created a draft pull request.
The pull request is with a script file and npm commands to run the scripts. I have used shell scripts for taking a dump from the database and restoring it for each test. And also the npm commands were included to run the scripts for each test run. The pull request is still in draft mode because of some issues I had when running the OpenMRS 3.0 in the docker environment. I had to bring a discussion for fixing this issue. Talk thread.
That’s about my experience during the fifth week in the coding period in Gsoc:2022. Next week I will be working on fixing the issues related to the docker. And also will be working on the other test cases to get them to the new repository after fixing them.
Thank you for reading the blog! See you in Week:6 Blog. :)
