look into in-memory Realm for tests #1131
Labels
Milestone
Comments
sosnovsky
added a commit
that referenced
this issue
Dec 1, 2021
tomholub
added a commit
that referenced
this issue
Dec 1, 2021
* issue 1111 only initialize Realm and KeyChainService once * wip * wip * wip * [skip ci] fixed controllers * [skip ci] more fixes * [skip ci] a few more * [skip ci] fix services * mail provider fixes [skip ci] * a few more fixes [skip ci] * a few more fixes [skip ci] * it builds * add to test scope * [skip ci] remove AppReset, fix some test usages * Project file fixed * removed unwanted files from test target * intermediate * fix * PR fixes * PR fixes II * less verbose backup service init * cleanup * controller cleanup * fix * cleanup * issue #1111 fix unit tests running * issue #1131 use in-memory Realm for tests * issue #1111 fix tests Co-authored-by: Ivan <[email protected]> Co-authored-by: Roma Sosnovsky <[email protected]>
|
This was already done in the referenced PR. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Also for testing we can use
in-memoryRealm instance, instead ofon-disk- it should be faster and doesn't need to be resetted, as it's new instance for each new test (https://docs.mongodb.com/realm/sdk/ios/test-and-debug/#testing)Originally posted by @sosnovsky in #1117 (comment)
I'm not entirely sure we use Realm in Swift tests. But will file an issue.
The text was updated successfully, but these errors were encountered: