Hi, is the Robolectric kotest extension abandoned?

# kotest

[nelson ramirez]

Hi, is the Robolectric kotest extension abandoned?

[sam]

I would say if @LeoColman is not maintaining it anymore, than yeah. We need someone from the community to step up.

[nelson ramirez]

Thanks @sam

[LeoColman]

I'm not. Robolectric was too much to me

[nelson ramirez]

Thanks @LeoColman, Getting robolectric to work well with junit5 is already difficult on it's own. I appreciate your effort!

[wasyl]

I’d say it’s pretty much impossible to have proper Robolectric support in JUnit5 right now: on one hand Robolectric only provides APIs for JUnit4, on the other JUnit5 doesn’t expose hooks for manipulating classpath for tests. So for now vintage runner + Robolectric rule is the only sane approach

[sam]

@LeoColman would you mind updating the repo to add a note to this effect and mark the repo as archived ?

[wasyl]

(the only better alternative is to ditch Robolectric completely)

[nelson ramirez]

I almost go things working yesterday, but ran into some MainLooper issues.

[nelson ramirez]

thanks @wasyl, Could you please expand on vintage runner + Robolectric rule as the only sane approach?

[wasyl]

It’s just the only officially supported way to run Robolectric. I was mistaken about the rule, I meant @RunWith(AndroidJUnit4::class) annotation for tests and writing oldschool @org.junit.Test tests

[wasyl]

and if you use JUnit5 in the project, you can do that by using vintage engine I think

[nelson ramirez]

Thanks, that's exactly the setup i currently have

[sam]

vintage engine allows you to run junit4 via junit platform yeah

[nelson ramirez]

and I wish there was a better alternative to robolectric for running android tests on a jvm, but alas. we work with the hand we're dealt

[nelson ramirez]

I appreciate the help fellas! have a good one