Hay my tests ran perfectly well on the machine. On making the pull request, github fails them because the there is some test(not my test) that fails and brings my PR fail to build successfully, PR_LINK . On closer look this test(edit-patient.spec.ts file) which is not mine fails to pass Anyone If u get time you look into it and maybe tell me what I’m missing out..
thanks @wedson ,
I added some comments on the PR
I saw them thank you very much @gcliff
1 Like
Hello Someone help me overcome this. After writing wonderful tests, on launching the server to test them,this happens
@gcliff
Are your tests pointing to dev3.openmrs.org, That error comes when there is an issue with 3.x module version(@openmrs/esm-framework and openmrs-esm-core) Developing frontend modules – O3 Docs
Possibly I am working on e2e tests on the ward-app under the esm-patient-management repo, does the problem occur on it also.
I could having wrong uuid’s of these[encounterType, location, provider] be the problem, If that’s the case can someone provide a documentation or provide them to me
@gcliff @chibongho1 @dennis and anyone out there
Thanks @wedson
Upgrade to node version v22.12.0
could you update to the latest main branch git pull --rebase upstream main and then yarn turbo build
Upgrade the core libraries yarn up openmrs @openmrs/esm-framework as @abertnamanya had recommended.
To run E2E tests, make sure the dev server is running by using:
yarn start --sources 'packages/esm-ward-app'
Then, in a separate terminal, run:
yarn test-e2e --headed
2 Likes
Bump core dependencies to their newest next tagged versions by running:
yarn up openmrs@next @openmrs/esm-framework@next
and try again
1 Like
I have suffered enough, somebody help me out. @gcliff the commands you provided at first worked perfectly but then ever since I changed the node version , This bellow happened
I can not proceed with running my tests. I have provided the console log it maybe of help pastebin
1 Like
hello @wedson from the logs you shared indicates a broken or corrupted file in your webpack installation. About the node version upgrade , been able to run the e2e ward up tests locally with node v22.12.0. Are you able to join the O3 coffee break today and we look deep into this ?
1 Like
even me i having issues there, the home page has been like this for 4days but i was waiting for when to pull code which is updated but it seems not yet
1 Like
absolutely yeah
1 Like
If any progress or solutions were discovered on the call, please share here in case someone in the future has similar problems and googles there way to this thread. 
thanks @burke , we found out that the versions needed to be bumped to newest tagged versions and there was need to make use of the patient object created via the playwright fixtures instead of creating one in the test spec files .
@wedson @elai you could provide feedback or progress if you were unblocked by the recommendations made in the call today
ok @gcliff