You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Not quite sure what we should do here, but out of the box LeakCanary runs in any debug environment. While we do support running LeakCanary in instrumentation tests, this is an intentional step that requires an extra dependency and config. It's not clear that the right default behavior is for LeakCanary to run in UI tests.
Is there a way to detect that we're running in UI tests?
In the mean time, we can recommend the following code in UI Tests:
When running with instrumentation turned on, this class will be instantiated for you before any of the application code, allowing you to monitor all of the interaction the system has with the application.
We could add an <instrumentation> tag to a subclass of Instrumentation, and if that is loaded then we know we're in tests
Not quite sure what we should do here, but out of the box LeakCanary runs in any debug environment. While we do support running LeakCanary in instrumentation tests, this is an intentional step that requires an extra dependency and config. It's not clear that the right default behavior is for LeakCanary to run in UI tests.
Is there a way to detect that we're running in UI tests?
In the mean time, we can recommend the following code in UI Tests:
The text was updated successfully, but these errors were encountered: