@MGaetan89 Great to know this good news, could you share the AGP link of this feature?

@MGaetan89 I think you can run unit-tests locally.

@MGaetan89 Great to know this good news, could you share the AGP link of this feature?

It's my understanding of the last comment in the issue that was in the test comment: https://issuetracker.google.com/issues/127986458#comment22

@MGaetan89 I think you can run unit-tests locally.

Yes, I can 🙂
I did it for some APIs before opening the PR, but apparently I missed something.

java.lang.RuntimeException: Failed to instantiate test runner class androidx.test.internal.runner.junit4.AndroidJUnit4ClassRunner

Looks like there are some dependencies issue?

The build is passing now 👍🏻

But is the :integration_tests:agp still necessary at all now? It basically declared an empty Activity that is started in a test. We do that in many other places, so probably the module can be removed too?

But is the :integration_tests:agp still necessary at all now? It basically declared an empty Activity that is started in a test. We do that in many other places, so probably the module can be removed too?

Merging this as-is, since it's already an improvement.

@utzcoz @hoisie what do you think about removing the :integration_tests:agp module completely?

@MGaetan89 IIRC, there are some modules use TestActivity of agp module in tests . If we can confirm that other modules don't depend on agp module, and we don't need extra basic tests, I prefer to deleting agp module.

I'll check again, but I didn't see any module depending on :integration_tests:agp or needing the TestActivity.