Week 03: GSoC’23 with OpenMRS
Hello Everyone,
Welcome back to my blog, where I share the latest updates from my Google Summer of Code (GSoC) project. The third week has come to a close, and I’m excited to bring you up to speed on the progress made. After completing my exams during the second week, I was eager to immerse myself back into the community and continue pushing forward. This week has proven to be highly productive, and I anticipate even greater accomplishments in the weeks to come. Without further ado, let’s delve into the updates.
Updates for the week:
The week kicked off with a Professional Development Call, where all the GSoC participants gathered to share their experiences thus far. It was an inspiring session as we had the opportunity to hear about the journeys and learnings of my fellow participants. Their insights provided valuable guidance and motivation for the weeks ahead.
In the Previous week I had created one Draft PR which has a failing tests. After discussing it in the QA squad call and with my mentors, we came to a conclusion that we should use two describe for patient registration component. Patient registration is the component is used for both i.e. for “new patient registration” and “updating the existing patient details”. So used two describes for the both the respective behaviours. One of the test for ‘edit the patient demographics’ was failing because of the mismatch in the ‘savePatient’ function parameters. So I fixed it with just expecting the necessary details i.e. the updated patient details. Because we only need to check if the patient details are getting updated or not and expected other object as anything. I changed the PR status from draft to ready to review. Now the PR is ready to review and will be merged after the successful. With the completion of this I am done with epic that I created for fixing the existing and skipped test under the patient management repo. Now we can move to writing the new test.
One more thing I need to tell you guys that we initially decided to use msw but my mentor faced some issue while configuring it with the O3 repos. So he created a talk post to further get this issue resolved. After the discussion he came to a conclusion that we will not be using MSW anymore. Here is the link to talk post of the discussion. Feel free to share your insights about this I would love to hear you take on this.
Last week I had two PRs open if you can remember one was for patient-registration component(about which we already discussed) and another one was for patient-registration-validation component. This PR got merged after few fixes. You can check this here.
This week was, I getting back to my community and it felt nice to be back but I faced few challenges also. One of them is that I am writing a test for the code which I haven’t written and it is taking time to understand the features and working. This is resulting into slow progress. I discussed about this with my mentors and they told me that we should reach out to developers with our queries and also take constant feedback from them.
I will surely follow that. That was it from my side for the week.
Goals for the next week:
In the upcoming week I will be writing some new tests and get the remaining PRs merged.
Thank you all for your support and feedback thus far. Your encouragement keeps me motivated as I embark on this exciting journey. Stay tuned for more updates on my progress, challenges, and lessons learned!
Happy coding to everyone, and have a fantastic week ahead!