I just can’t remember how to use the robolectric r...

# minutest

[dmcg]

I just can’t remember how to use the robolectric runner and I’m lazy, was hoping you could remind me about the annotations etc

[dave08]

Oh, I guess my own example won't speak any better than this: https://developer.android.com/training/testing/set-up-project

Thanks for wanting to check this... 🙂

[dmcg]

Ah, I think I remember why I didn’t bite the Minutest bullet in that entire blog post series!

@RunWith(AndroidJUnit4::class)

[dmcg]

@RunWith(MinutestJUnit4Runner::class)
abstract class JUnit4Minutests

[dmcg]

So there are 2 test runners declared if you say

@RunWith(AndroidJUnit4::class)
class MyTests : JUnit4Minutests()

[dmcg]

MinutestJUnit4Runner synthesises the tests from the rootContext, but AndroidJUnit4 won’t have run it to do that.
Unfortunately a runner is the only way in JUnit 4 to make new tests. I think that AndroidJUnit4 could be a Rule, but it isn’t,
I suppose because it goes on to use rules to implement other features and it would just have been hard.

[dmcg]

I had worked on the principle that Google would have gotten JUnit 5 support nailed.

[dmcg]

What I’ve done with Spring is delegate to the recalcitrant runner code from a context builder

[dave08]

Thanks again for looking into this! Now it makes sense... I just don't really understand that last comment...?

[dmcg]

Sorry, overly pretentious! Test runners generally hack the test lifecycle (bringing up environments before tests run for eg). In minutest we can do that with a context builder extension method, and so for Spring I wrote a springFixture clause that delegated to the code that the Spring test runner was invoking