# GSoC 2023: Enhancing Component Test Coverage and Quality for OpenMRS3 Project updates and discussions **URL:** \ **Category:** Quality Assurance\ **Tags:** qa, gsoc2023, o3\ **Created:** [May 22, 2023, 4:06pm UTC](https://talk.openmrs.org/t/gsoc-2023-enhancing-component-test-coverage-and-quality-for-openmrs3-project-updates-and-discussions/39691 "2023-05-22T16:06:30Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![ayushmishra](https://talk.openmrs.org/user_avatar/talk.openmrs.org/ayushmishra/32/17973_2.png) [@ayushmishra](https://talk.openmrs.org/u/ayushmishra)\ **Post date:** [May 22, 2023, 4:06pm UTC](https://talk.openmrs.org/t/gsoc-2023-enhancing-component-test-coverage-and-quality-for-openmrs3-project-updates-and-discussions/39691/1 "2023-05-22T16:06:30Z")
Hello Everyone, I will be working on the project [GSoC 2023: Enhancing Component Test Coverage and Quality for OpenMRS3](https://wiki.openmrs.org/display/projects/GSoC+2023%3A+Enhancing+Component+Test+Coverage+and+Quality+for+OpenMRS3). This project will aim to achieve a high level of test coverage for O3 repos (patient-chart and patient-management will be primary repos) by using consistent and comprehensive unit and integration testing strategy. The key areas of improvement for this project include: 1. Test Coverage: By identifying areas of the codebase with insufficient test coverage, we will work towards achieving a higher level of confidence in the quality and stability of the O3 repositories. This will involve writing new tests and enhancing existing ones. 2. Consistency: A consistent testing strategy ensures that tests are structured uniformly across the codebase. By adhering to established guidelines and best practices, we will create a reliable and predictable testing framework. 3. Comprehensive Testing: The project aims to cover a wide range of scenarios, including edge cases and potential error conditions, to ensure the robustness of the code. By considering various use cases and testing different aspects of the system, we can provide more comprehensive protection against potential issues. **Mentors** Primary Mentor: @piumal1999 Backup Mentor: @anjisvj **Resources** 1. Project Details: [Link](https://wiki.openmrs.org/pages/viewpage.action?pageId=313327996) 2. Testing strategy docs: [Link](https://wiki.openmrs.org/pages/viewpage.action?pageId=313328159) 3. Meeting Notes: [Link](https://docs.google.com/document/d/1YOqTFF0H0_EkDWa-njcOsooyQQh_t78kmv5tSqHJUlk/edit?usp=sharing) 4. Meeting Link: [join here](https://meet.google.com/wfc-ebry-bfh) We have weekly call for discussion about the project. Everyone is invited to join and be a part of discussion. I am eager to have discussion with you all regarding this project. Meeting details are given below: GSOC’23 - Enhancing Component Test Coverage and Quality for OpenMRS3 Weekly discussion Wednesday, May 31 · 7:00 – 8:00pm Time zone: Asia/Kolkata Video call link: [https://meet.google.com/wfc-ebry-bfh](https://meet.google.com/wfc-ebry-bfh) Thank you for your support, and I welcome any suggestions or advice as I embark on this exciting journey.@jayasanka @jennifer @grace @ibacher @dennis @vasharma05 @hadijah315 @kdaud @piumal1999 @anjisvj ---
**Author:** ![ayushmishra](https://talk.openmrs.org/user_avatar/talk.openmrs.org/ayushmishra/32/17973_2.png) [@ayushmishra](https://talk.openmrs.org/u/ayushmishra)\ **Post date:** [May 31, 2023, 4:45am UTC](https://talk.openmrs.org/t/gsoc-2023-enhancing-component-test-coverage-and-quality-for-openmrs3-project-updates-and-discussions/39691/2 "2023-05-31T04:45:29Z")
Hello Everyone, The coding period has started, and I am excited to provide updates on the project progress during the community bonding period. I joined the onboarding call and gained lot of insights on how to complete my gsoc successfully. Then I had meeting with my mentors @piumal1999 and @anjisvj in which we discussed about the project the scope and the timeline. Most of the things are same as I proposed. Mentors are very helpful and explained how should I work efficiently. They also clarified more about the project and how should I proceed with the project. I was working on improving the existing tests and created an epic for that. [Here](https://issues.openmrs.org/browse/O3-2063) is the link. I completed almost all the issues and created PR for all the issues out of which three of them are under review. The links to the PR which I created during the community Bonding Period:- > > > \## Requirements > > \- \[x\] This PR has a title that briefly describes the work don…e including the ticket number. If there is a ticket, make sure your PR title includes a \[conventional commit\](https://o3-dev.docs.openmrs.org/#/getting\_started/contributing?id=your-pr-title-should-indicate-the-type-of-change-it-is) label. See existing PR titles for inspiration. > \- \[\] My work conforms to the \[\*\*OpenMRS 3.0 Styleguide\*\*\](https://om.rs/styleguide) and \[\*\*design documentation\*\*\](https://zeroheight.com/23a080e38/p/880723-introduction). > \- \[\] I checked for feature overlap with \[\*\*existing widgets\*\*\](https://om.rs/directory). > > > \## Summary > > In this PR, I tried to update the failing tests which was getting skipped. The test was failing because the error text was not coming when input field was left empty. I tried to fix those by mocking the input component. I also mocked the formik component. > > \