A way to apply JUnit's @Category to auto-generated tests from Compose Preview

[hellohj]

Thank you for your help as always. This filter @category has resulted in a significant reduction in CI snapshot testing time.

While trying out Compose Preview auto-generated tests, I don't seem to find a way to add JUnit @Category filter because there is no actual written test. Do you have any ideas or suggestions how we only run snapshot tests without running other unit tests in a module for auto-generated snapshots? Would appreciate your insights.

[takahirom]

Thank you for reporting this. If you want to filter it, you can specify the test class like --test "com.github.takahirom.roborazzi.RoborazziPreviewParameterizedTests.test". Or we could use excludeTestsMatching() in Gradle DSL. But I think it might be good to have such a category.

We have some options to fix this:

1. We could add a default Category like @Category(RoborazziComposablePreviewTestCategory::class). RoborazziComposablePreviewTestCategory will be in the Roborazzi library.
2. Or we could add a Gradle DSL: roborazzi { testFunctionAnnotations = "@junit.Category(xxxx.xxxx.xxx.Xxx)" }
   Do you have any opinion on this?

[hellohj]

Thanks for checking this out. Option 1 seems easiest for me, since I'm not very experienced with Gradle. We already use a custom Category class to filter tests, so adding 'RoborazziComposablePreviewTestCategory' would be pretty easy.

[hellohj]

@takahirom Is there a timeline for this change? Thank you!

[takahirom]

Thanks. I'm planning to release a large update for Compose Preview support, and this update will conflict with that implementation, so we cannot work on this for now. Currently, we need a code review of the implementation—at least its architecture. If you have time to review it, it might help us expedite its release.
#633