Lines Matching +refs:android +refs:activity +refs:class

18 androidTestImplementation "com.squareup.leakcanary:leakcanary-android-instrumentation:${leakCanaryV…
24  class CartTest {
45 │ GC Root: System class
47 ├─ com.example.MySingleton class
48 │    Leaking: NO (a class is never leaking)
51 ├─ android.widget.TextView instance
52 │    Leaking: YES (View.mContext references a destroyed activity)
77  class CartTest {
91  class CartTest {
112  class CartTest {
132  class CartTest {
169   .around(ActivityScenarioRule(CartActivity::class.java))
176 finishes the activity at the end of a test, having `DetectLeaksAfterTestSuccess` around
177 `ActivityScenarioRule` will detect leaks after the activity is destroyed and therefore detect any
178 activity leak. But then  `DetectLeaksAfterTestSuccess` will not detect fragment leaks that go away
179 when the activity is destroyed.
184   // Detect leaks AFTER activity is destroyed
191 activity leaks will not be detected as the activity will still be created when the leak assertion
197   .around(ActivityScenarioRule(CartActivity::class.java))
198   // Detect leaks BEFORE activity is destroyed
208 // Detect leaks BEFORE and AFTER activity is destroyed
212   .around(ActivityScenarioRule(CartActivity::class.java))
220 // Detect leaks BEFORE and AFTER activity is destroyed
225     around(ActivityScenarioRule(CartActivity::class.java))