GSoC Journey: Week 10 of Coding Period
Hello folks,
Myself Senthil Athiban, a final year undergraduate student at Madras Institute of Technology. This blog represents a continuous series documenting my journey through GSoC. If you haven’t already read my previous blogs, I encourage you to check out my previous blogs here. I have been selected as a GSoC student at OpenMRS for the Validation Rule Builder for the Form Builder project. My primary mentor is Dennis Kigen, and my backup mentor is Hadijah Kyampeire.
GSoC Admin Meeting
On the first day of week 10, I had a meeting with our GSoC admin at OpenMRS. We discussed our blockers, challenges, and had some fun chat. Our GSoC admin, Jayasanka Weerasinghe, was very friendly and offered suggestions, such as extending our coding period if needed, and provided other helpful advice. He also emphasized the importance of writing test cases and documentation for our project. Thankfully, I had already started writing documentation and test cases parallelly while building the validation rule builder, and I received appreciation from the GSoC admin for my progress.
📅 Week 10: July 29 — August 03
Tasks to be Completed:
- Review Changes & Bug Fixes: Fix bugs through manual testing and implement changes based on mentor feedback.
- E2E Test: Cover E2E test cases for the validation rule builder.
Tasks Completed:
✅ Review Changes: Made adjustments based on mentor feedback.
✅ Testing: Covered E2E test cases for various validations, such as hideWhenExpression, failsWhenExpression,allowing or disallowing future dates and decimal values and calculation logic.
Lessons Learned:
The purpose of E2E test cases is to ensure the workflow of a feature is functioning correctly. These tests are added to the GitHub workflow to validate incoming PRs. While not particularly difficult, E2E testing is crucial. So, I began practicing E2E tests before covering my feature. Sometimes the tests pass, and other times they fail. For example, tests may pass on the local machine but fail in CI. I later realized that debugging skills are essential when writing E2E test cases. Thankfully, the Playwright documentation helped me resolve issues while writing E2E tests.
Plans for Next Week:
- Manual Testing: Conduct thorough testing of the validation rule builder with complex form logics to ensure functionality and reliability.
About Me
I’m Senthil Athiban, a final-year undergraduate student from India. By day, I play with VS Code by building new projects, and by night, I contribute to projects on GitHub. My journey is driven by a passion for software development and a curiosity to explore new technologies.
🔗 Connect with Me
- GitHub: senthil-athiban
- LinkedIn: Senthil Athiban M
- Twitter: @senthil_k8s
