Would <Burst> be a good way to get around an issue...
# squarelibraries
e
Would Burst be a good way to get around an issue in JUnit4 where I want to use TestParameterInjector but also AndroidJUnit4?
j
Yes
🆒 1
Although
AndroidJUnit4
doesn't provide you with much in the first place. You can replicate almost anything it does with a regular rule.
e
It was just an easy way to not have issues when testing code that uses something from the Android SDK
j
Is this for an instrumented test? Or a host-side test with Robolectric?
e
Host side with Robolectric, but I'm not explicitly using anything from Robolectric
anyway i'm not trying to talk you out of Burst or anything
just interested in the motivation
e
I saw that a few days ago, but for some reason something feels off about that. Also it would be cool to use Burst across my KMP and Android-only projects
It worked! Now if only Robolectric tests didn't take 10x longer to run 😬
🦜 1
j
Well hey at least they're 10x faster than instrumented ones
âž• 2
a
RobolectricTestParameterInjector
was just added in the
4.14-beta-1
release of Robolectric, which integrates the
Robolectric
runner with
TestParameterInjector
. I'll need to try out Burst to see how they compare