You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the input files that the test uses result in a number of warnings from "INVALID_MSG_CONDITION_MAPPING". During the test the final response from the history submission endpoint is output into the terminal. Example run: 525 lines of output from the test, ~200 lines of this are warnings. The valid_hl7_e2e.hl7 file produces 12 warnings from missing mappings and so inflates the output of the test by a lot.
What you need to know
There are two options to fix this:
Change the loinc codes used in the test files so that the mapping warnings are gone.
This may be best practice as we should be using valid data for these tests.
Modify the test so that the history endpoint response is only logged when there is an issue.
This may be preferable in the long term as there are currently 3 scenarios for this test in master with 2 more being added soon.
Acceptance criteria
The noisy output from the end2endup test is reduced.
The text was updated successfully, but these errors were encountered:
Problem statement
Currently the input files that the test uses result in a number of warnings from "INVALID_MSG_CONDITION_MAPPING". During the test the final response from the history submission endpoint is output into the terminal. Example run: 525 lines of output from the test, ~200 lines of this are warnings. The valid_hl7_e2e.hl7 file produces 12 warnings from missing mappings and so inflates the output of the test by a lot.
What you need to know
There are two options to fix this:
Acceptance criteria
The text was updated successfully, but these errors were encountered: