Add the option to initialize the ResourceDao for testing. #17
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
…when updating a resource.
Add basic support to database modes.
Add the possibility to delete the database.
…it possible to test code that uses the fhir_db as caching solution (e.g. integration tests).
Dokotela
added a commit
that referenced
this pull request
Aug 5, 2021
fhir_auth export package consistency
…-db-factory-for-testing
|
Ended up adding this manually, but should now be included. Let me know if there are issues! |
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.
Scope of the PR
Add an additional optional value to state that the
ResourceDaois being used for testing.This is using sqflite_common_ffi under the hood to mock the underlying sqflite database.
Goal
Make it easier to write integration tests for functionalities that use the
fhir_db.What is the additional noise
I pulled main into
devto make sure that we are not missing any functionality that has been merged directly intomainwithout being merged todevfirst.This is the reason you see changes in files that are not in the scope of this PR.
Edit:
If this is fine I can add myself the same changes in the other places (
dstu2,r4, ...)