Deepankar Bhardwaj

Fixes #17

@epicadk is working on this.

Not in UI - since the SDK doesn't have any. I think something like the medium tests mentioned here: https://developer.android.com/training/testing/fundamentals#medium-tests From the above link: > Tests in your app's repository...

A clarifying question: Does multiple `process` include multiple `threads`? If so then `FhirEngine` should implement some kind of upload queue. We can discuss the design further. In case it might...

IMHO `FhirEngine` is too big to take a first shot at. I suggest you at the existing tests for any `Dao` or sync and send an improvement PR first.

Here's the android client webpage: https://hapifhir.io/hapi-fhir/docs/android/client.html. An objective comparison - pros and cons of each - would be helpful. E.g. Retrofit | hapi-fhir-android --------|------------------ Commonly used android lib hence easy...

> @deepankarb why did you choose jacoco over codecov in your PR? > > @pld do you have any particular recommendations? Thanks! Jacoco generates the code coverage reports both offline...

#502 Adds code coverage metrics. Keeping this issue open to track progress to > 95% coverage.

This is a big limitation. I am using snappydb to write logs. This means while logging is going on I can't use the db for other (primary) purposes, which breaks...

Would like to add to the above comment that snappydb is a really cool lib. Thanks a ton!