Open BenHenning opened 2 years ago
Note that while we can introduce a TestActivity today, it's a bit painful to use broadly since it'll require introducing a bunch of custom injectors throughout the codebase. We may want to wait until #1720 is introduced so that injectors can be automatically generated (via entrypoints) which will simplify stuff a lot.
I couldn't find an issue tracking this already, so filing a new one.
We can avoid the pattern of needing to introduce custom test activities & fragments throughout the codebase by introducing a general-purpose test activity & fragment that can be trivially added to stage different UI scenarios.