https://kotlinlang.org logo
Join Slack
Powered by
On my go and I will be later near laptop but looks...
# testballoon
e
On my go and I will be later near laptop but looks like newest Robolectric is not compatible with TestBallon
👀 1
o
They have introduced a public ABI change without increasing the major version. The fix is simple: Adding a 4th parameter 
emptyList<MethodHandleDecorator>()
to this place. The question is now: Are Android folks used to unconditionally update to the lastest Robolectric or is there a backward-compatibility story?
e
I would say we are probably more updating uncoditionally since this release is trying to catch up with the latest Android API released this summer.
o
Okay, and to be fair, it's a package designated as `internal`: 
package org.robolectric.internal.bytecode;
So if this doesn't break anything else, I could easily update the Robolectric version.
e
If you have version to test (or I can build locally myself) to confirm
o
I can publish a snapshot for you to test.
e
Sure and thank you! Do you want me to create GH issue?
o
Thanks for the offer! in this case, I could easily do so on my own. I already have all the information available, so you don't need to replicate the research.
kodee happy 1
Side note: They still haven't managed to ship their JUnit 5 Platform/Jupiter integration.
e
Next month I’m free from all my pet activities and I will try finally to contribute to the ecosystem
o
What's your plan? I guess you already did a great service with your article. I'll be talking about TestBalloon for Android at droidCon Berlin, and I'm intending to mention your experiences.
👍🏼 1
e
Plan to try Paparazzi with TestBallon. And look into junit4 Google setup around connected tests and find possibility to free that from junit coupling if possible. Maybe also try to contribute to Robolectric in the same fashion.
o
Cool! Do you plan to head to Berlin for droidCon?
e
No, unfortunately, not this year. One of my favourite Android conference and the city. But this year I decided that financial wise I have other priorities.
o
Yeah, for me it's more or less in the neighborhood, so I'm trying to keep folks informed that they don't have to get stuck in the age of dinosaurs. 😉
e
haha, looking for amount of tests we have on our project - this dinosaur caught us too strong. Even most of our unit tests are jupiter junit.
o
Sure. The entire ecosystem was somewhat under-powered in testing, as if it was still Java. And Android with JUnit 4 is hit particularly hard. Of course, this will not change over night, but I guess I need to do more to just spread the word. The conference is one thing. Another would be to post more articles. And by the way, would you mind me posting a short summary and link to your article in the TestBalloon blog?
The snapshot is now available via Maven Central Snapshots:
Copy code
maven("<https://central.sonatype.com/repository/maven-snapshots/>")
Version is 
1.2.0-Beta2-20260916.192306-7
junit4 Google setup around connected tests and find possibility to free that from junit coupling if possible
What would this unlock? Is there a limitation with connected tests related to TestBalloon?
e
Sure, feel free to do what you want and feel right
thank you color 1
I will try today
Thank you!
kodee welcoming 1
Hey hey, sorry for a long delay - it works!
o
Excellent! Could you also enlighten me on that one?
> junit4 Google setup around connected tests and find possibility to free that from junit coupling if possible
What would this unlock? Is there a limitation with connected tests related to TestBalloon?
e
I was mixing things. I was influenced that I need rules to run Android and Robolectric tests (for robolectric the junit4 is required).
👍 1
o
Yes, and even more so for instrumented tests.
2 Views
Open in Slack
PreviousNext
Powered by