Marcel Schnelle

This is fantastic work, @warnyul – I'm able to confirm that this does indeed work for a simple use case that I just spun up. Great job!

I was able to resolve the same issue in an unrelated context and have shared my insights [in the linked ticket](https://github.com/spotify/android-sdk/issues/226#issuecomment-1722253294). Hopefully it may help y'all as well!

I have encountered these particular noisy logs on a totally unrelated OSS project that I maintain ([link to the issue in that project](https://github.com/mannodermaus/android-junit5/issues/291)). My research eventually led me here, but...

Thank you for the swift review! 🙇‍♂️ I will address the CI failure shortly and consider extending the unit tests.

@takahirom お待たせしました。We should be good to go with another run of the workflows. I reinstated the basic JUnit 5 detection of the stack trace strategy in the latest commit https://github.com/takahirom/roborazzi/pull/355/commits/0d8c86edad33cf61c1d832b7adf7e4cd8b1902cd,...

Absolutely, sounds like a solid plan. I'll need a bit of time for this, but I'll let you know once done.

@takahirom I'm thinking about the `RoborazziRule` and whether or not to make a similar functionality available with the JUnit 5 integration as well (since you wouldn't be able to use...

Seems like we have a compatibility issue because the Robolectric JUnit 5 extension is built against Java 17, while Roborazzi uses the more conversative Java 11. 🤔 AGP has had...

@takahirom I wrote a doc section on JUnit 5 in the latest commit (first time using Writerside; pretty neat!) and also updated the Robolectric extension to the latest version. It's...

Hey, apologies for the late response. Would you mind sharing a bit of your app module's build script file? I'd like to see how the plugin is integrated into the...