<@U54CM9PGS> I think I understand when the tests g...

# testballoon

[dave08]

@Oliver.O I think I understand when the tests get "flattened" in intellij's test runner now... I just disabled junitplatform on my android host tests, and now they all appear flat, even though when it was enabled they were nested... I guess that's the junit4 limitation there... but I'm wondering why in the docs you say that junit4 support is preferred for those tests?

[dave08]

Now after I updated to agp 8.13 and gradle 9.4, I get TestBalloonJunit4 > TestSession (down arrow) @Default > package name.class name > class name (down arrow) test name...

which is still very long... but I guess that's the issue you opened.

[dave08]

and at least it's nested and not all on one very big line

[dave08]

Also I update the intellij plugin before running the tests to the new 0.6.0 version

[Oliver.O]

I'm wondering why in the docs you say that junit4 support is preferred for those tests?

The entire Android testing ecosystem is based on JUnit4. For example, using JUnit 4 rules requires it. So if that's fully supported, why add additional complexity with JUnit 5 to the mix?

[Oliver.O]

which is still very long... but I guess that's the issue you opened.

Yes. It just needs some time to sort this out.

[dave08]

I'm not sure what made the results nested though... the gradle upgrade to 9.4 or the agp version.

I also had a little problem with tests not being found, in the end it happened to be because I added exclude testBalloon to all test source sets in my kmp project instead of only the android host tests that have junit4 and platform enabled. I looked a few times in the getting started section and didn't see anything about that... I really think that all the setup/running details should be in a getting started section and not buried in the Integration section after explaining the usage of the library and the getting started section could be split into getting started (which is really only initial configuration and setup) and then another "usage" or "writing tests" section that only has usage docs. that way users first go through all the setup steps they need and when they get to using the library everything will just work...

[Oliver.O]

because I added exclude testBalloon to all test source sets in my kmp project instead of only the android host tests that have junit4 and platform enabled

That's actually a very complex (and not recommended) setup, which is definitely no candidate for "getting started". Mixing JUnit 4 and 5 on the Android side was never easy. While it can be done, a number of factors have to be considered and it's easy to accidentally break things.

[Oliver.O]

Other than that, any feedback on using Robolectric with TestBalloon?