-
-
Notifications
You must be signed in to change notification settings - Fork 210
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
Add additional tests for Enketo Form functionality #7600
Labels
Milestone
Comments
jkuester
added
Type: Technical issue
Improve something that users won't notice
Enketo
Affects Enketo forms
labels
Apr 25, 2022
Is this still valid @jkuester ? If yes, should we give send it to |
Thanks @jkuester . |
Looks like this issue is in Allies Code Health, please work with @mrjones-plip to organize. |
11 tasks
m5r
added a commit
that referenced
this issue
Sep 11, 2023
tatilepizs
added a commit
that referenced
this issue
Sep 19, 2023
Ticket: #7600 This commit: * Submit a form with a non-relevant inputs group. Verify the data in the inputs group is still saved. * Submit a form with fields in the inputs group to have a constraint that is violated when saving the form. Verify that the form still saves properly since the inputs group is not relevant. * Submit a form that uses data loaded from the patient's contact-summary and verify the contact summary data is properly loaded. * Submit a form using the instance::db-doc and instance::db-doc-ref functionality and verify the new reports are properly created along with the expected doc-refs. * Submit a form with a required tel field and verify this is properly handled by the phone-widget proper and the report is saved. * Create a completely new test using the enketo widgets we don't have in our forms.
Merged into |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Describe the issue
During AT for #6345, there were a number of behavior issues that were found that were not covered by any sort of automated tests. It would be very beneficial to have automated tests for these cases before the next Enketo uplift in #7599.
inputs
group. Verify the data in theinputs
group is still saved.inputs
group to have a constraint that is violated when saving the form. Verify that the form still saves properly since theinputs
group is not relevant.contact-summary
(e.g. the defaultdelivery
form loads in the pregnancy UUID). Verify the contact summary data is properly loaded (e.g. that the pregnancy UUID is saved for thedelivery
report).instance::db-doc
andinstance::db-doc-ref
functionality and verify the new reports are properly created along with the expected doc-refs. (e.g. new contacts are created for the babies entered into the defaultdelivery
form.)required
tel
field and verify this is properly handled by thephone-widget
proper and the report is saved.The text was updated successfully, but these errors were encountered: