Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

O3-2311: Resolve resource limitation issues in e2e tests #1304

Merged
merged 2 commits into from Aug 7, 2023

Conversation

Piumal1999
Copy link
Collaborator

@Piumal1999 Piumal1999 commented Aug 5, 2023

Requirements

  • This PR has a title that briefly describes the work done including the ticket number. If there is a ticket, make sure your PR title includes a conventional commit label. See existing PR titles for inspiration.
  • My work conforms to the OpenMRS 3.0 Styleguide and design documentation.
  • My work includes tests or is validated by existing tests.

Summary

With this PR, we can avoid resource limitation issues in GitHub actions. When the e2e tests are running, it will automatically create a lightweight prod version of the front end (as a docker image), only containing the patient-chart MFs and the necessary MFs. So it can run with less RAM. That docker image will be used to create the frontend instance of the e2e docker-compose stack. This will also reduce the loading durations.

However, it takes around 35 minutes to complete the job. I'm working on to reducing it by using the pre-filled backend images.

Screenshots

image

Related Issue

https://issues.openmrs.org/browse/O3-2311

Other

Currently, the e2e Github action workflow is disabled. We can enable it after optimizing it.

@Piumal1999 Piumal1999 marked this pull request as ready for review August 5, 2023 18:28
@Piumal1999 Piumal1999 changed the title O3-2311: Resolve resource limitation issues in patient chart e2e tests O3-2311: Resolve resource limitation issues in e2e tests Aug 5, 2023
@ibacher ibacher merged commit 0706919 into openmrs:main Aug 7, 2023
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants