Adding Testing Harness #6
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…hod from the class DocFhir. This change serves to de-couple the file conversion code from the container running it.
… add it to. In fact, it should probably take a File output_file instead.
…o use a destination file of (original)-FHIR.xml if out_filepath is not given.
…f DocFhir returns a success/fail boolean.
…stant API methods. Also, added apache commons-io to dependency.
…quired, there should be a method constructor that does this. Currently, instance initalization seems to be a seperate method from the constructor, which is confusing and causes errors.
…g XMLUnit to compare FHIR xml while ignoring whitespace (which is irrelavent to xml).
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
These commits add a testing harness to DocFhir. What this means is that a tester can create docGraph test data and FHIR expected results data. The test data will be converted to FHIR format and compared against the expected results. This comparison assumes the output is XML and ignores white-space. Test cases are added and removed by simply adding and removing files from their respective folders. This testing is NOT unit testing. It only tests that the final output of the program is correct. It does not test whether the programs individual methods work correctly in all cases.