-
Notifications
You must be signed in to change notification settings - Fork 228
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
(fix) O3-2284: Fix failing patient registration test #763
Conversation
example.env
Outdated
@@ -1,5 +1,5 @@ | |||
# This is an example environment file for configuring dynamic values. | |||
E2E_BASE_URL=http://localhost:8080/openmrs | |||
E2E_BASE_URL=https://dev3.openmrs.org/openmrs |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd prefer if the example setup didn't point at dev3. We need to limit the usage of dev3 for automated testing.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@@ -77,7 +77,7 @@ export const generateRandomPatient = async (api: APIRequestContext): Promise<Pat | |||
], | |||
attributes: [], | |||
birthdate: '2020-2-1', | |||
birthdateEstimated: true, | |||
birthdateEstimated: false, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this change necessary?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah. If we use birthdayEstimated
as true
, it will take the patient as a "patient with an unknown birthdate". So when we go to the edit patient page, it will automatically use the "Birthdate unknown" option.
(That change was added with 7dbf922. And the tests were failing after that)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
PS While it may not matter much, it's less ambiguous (and more likely to work everywhere) if we stick to ISO 8601 for dates, i.e., 2020-02-01.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, that's right. I changed the date format.
Co-authored-by: Ian <[email protected]>
* Dynamic frontend Docker image for e2e test * Change directory * Fix tests * Update e2e/support/github/run-e2e-docker-env.sh Co-authored-by: Ian <[email protected]> * Update e2e/support/github/Dockerfile Co-authored-by: Ian <[email protected]> * Fix the port numbers * Remove unwanted MFs * Remove unwanted MFs * Remove unwanted MFs * Remove unwanted MFs * Remove unwanted MFs * Test only with login and home apps * Test with navigation, chart and home apps * (Breaking) Revert the changes related to #763 --------- Co-authored-by: Ian <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Piumal1999 I merged latest changes to your PR and reran tests. All the test cases are passing now.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @Piumal1999 !
Requirements
Summary
Fixed the failing patient registration e2e test:
Screenshots
None.
Related Issue
https://issues.openmrs.org/browse/O3-2284
Other
None.