Hi all, here’s another project idea:
GSoC 2023: An effective unit & integration test strategy for OpenMRS3
Introduction
OpenMRS consists of several micro frontend modules and repositories, most of which have unit and integration tests written by individual developers. However, these tests exhibit inconsistencies due to the diverse testing strategies used by different developers. To address this issue, there is a need for a consistent and comprehensive test strategy or framework for the unit and integration tests of OpenMRS3, aimed at achieving a high level of test coverage.
Objectives:
Implementing an effective unit & integration test strategy for OpenMRS3.
Expectations:
- Develop a comprehensive testing strategy that can be applied to all OpenMRS3 micro frontends.
- Determine what to test (e.g. In react → props, state, rendering, event handling, error handling)
- Specify testing method (e.g. libraries, mocks, stubs)
- Ensure test coverage (e.g. edge cases, positive and negative scenarios)
- Document the strategy
- Outline the necessary tests based on the strategy (including a draft for a single repository in the project proposal)
- Upgrade existing tests to align with the new strategy
- Implement any missing tests
- Resolve any bugs in the current tests.
Further improvements (Optional):
Improve the code quality testing mechanism (ex: eslint)
Project Size:
Medium
Skills required:
Familiarity with OpenMRS microfrontends (including setup and directory structure) Background in microfrontend development Proficiency in testing techniques
Final Outcome:
A robust, well-documented unit and integration testing strategy for OpenMRS3 microfrontends To be used as a reference by developers in future development efforts.
Note: Since we have enough time before the GSoC student application period, we can introduce the test strategy by ourselves and make the project more focused on test coverage instead of the test strategy. Editable doc: GSoC 2023: An effective unit & integration test strategy for OpenMRS3 - Google Docs