Week 08: GSoC 2022 with OpenMRS

Coding Period Week 08

Pasindu Rupasinghe
3 min readAug 6, 2022
Gsoc:2022 with OpenMRS

Hello Everyone.

We are in the eighth week of the coding period in Gsoc:2022. In the previous week, we worked on solving the issues related to the 3.x existing test scenarios. Also, we had our mid-term evaluation as well. You can read the past week’s blog post here. I’ll be sharing the experience of this week in this blog post.

This week I had to work on mainly two objectives of the project epic. Those are,

  1. Setup a corn job schedule for the GitHub workflows and simplify the script running method. Jira ticket
  2. Update the cypress version to the latest stable version. Jira ticket

Setup a corn job schedule for the GitHub workflows and simplify the script running method
The GitHub actions will currently only execute in the 3.X test repository when a PR is active for the repository. The GitHub procedures will execute on a fixed schedule thanks to the setup of a corn job. The test cases will be run on a daily basis with this cron schedule. Therefore, users will be able to verify the 3.x components’ daily status.

Cron schedule for the login workflow

Additionally, this pull request includes a minor implementation that simplifies the script execution process. Basically, by moving the script runner to a centralized location (commads.js), the script runner may be made simpler. Additionally, we don’t need to use npm to run the bash command it executes directly using cy.exec ().

Pull request:

Update the cypress version to the latest stable version.

10.4.0 is the most recent stable version of Cypress. We are using a less advanced Cypress version in the QA testing framework. Hence this issue affects some causes such as hooks not working properly, and the screen recording functions not working properly. Cypres 10 is now with the component testing feature. For 3.x we are using End-to-End testing.

With this implementation, the organization requested to have a .lock file in the repository. So this suggestion was to have a yarn.lock file in the repo. So I had to change the package manager from npm to yarn. So the process is ongoing. And the pr will get be on review soon.

Pull request:

Thank you for reading! See you in Week:9 Blog. :)

--

--

Pasindu Rupasinghe

Undergraduate at University of Colombo School of Computing.