Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Release RunTestInLooperThread as a separate artifact #5657

Open
Zhuinden opened this issue Jan 3, 2018 · 3 comments
Open

Release RunTestInLooperThread as a separate artifact #5657

Zhuinden opened this issue Jan 3, 2018 · 3 comments

Comments

@Zhuinden
Copy link
Contributor

Zhuinden commented Jan 3, 2018

Goal

What do you want to achieve?

Verify RealmResults containing expected data in automated integration tests

Expected Results

This should be easy

Actual Results

You need to copy out a bunch of Realm internal stuff! 馃槃

It'd be nice if Realm either ran in JVM without Android (but that won't happen anytime soon, ofc)

or could provide a plug-and-play "testing" helper with which you can verify Realm notification after transactions and query results.

Version of Realm and tooling

Realm version(s): 4.3.1

Realm sync feature enabled: no

@cmelchior
Copy link
Contributor

Can you elaborate a bit more on the use case? JVM aside (which would be nice for speed reasons), then I would assume you could just do normal JUnit asserts?

@Zhuinden
Copy link
Contributor Author

Zhuinden commented Jan 4, 2018

@cmelchior
Copy link
Contributor

Ah, like that. Yeah, we have considered doing that actually, but it has rather low priority, unfortunately.

But yes, callback testing in unit tests is rather annoying. I'm actually a bit surprised that no-one has created a generalized library for that yet. We cannot be the only one with that requirement.

@cmelchior cmelchior changed the title Possible improvement: Realm testing module Release RunTestInLooperThread as a separate artifact Jan 4, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants