Published
Espresso does most of the heavy lifting for you when it comes to detecting when the UI is idle. But if you're using any custom background threads or scheduling for long running jobs, you might need to add and manage an IdlingResource to tell Espresso when your app is busy and when it's idle.
Watch more episodes of Android Testing Patterns here:
Subscribe to the Android Developers channel at
Watch more episodes of Android Testing Patterns here:
Subscribe to the Android Developers channel at
- Category
- Phone
Sign in or sign up to post comments.
Be the first to comment
Up Next
-
03:03
AdapterViews and Espresso - Android Testing Patterns #3
-
02:59
Android Performance Patterns: Why 60fps?
-
03:08
Android Testing Support - Android Testing Patterns #1
-
00:18
Google for Devs free resource? Yes, please. ????
-
03:03
Android Performance Patterns: Rendering Performance 101
-
03:18
Android Performance Patterns: Overdraw, Cliprect, QuickReject
-
56:08
Dan Andrews: "NASA at Google: Resource Prospector" | Talks at Google
-
05:45
Android Performance Patterns: Garbage Collection in Android
-
04:40
Android Performance Patterns: Battery Drain and WakeLocks
-
05:34
UI testing with Espresso - Android Testing Patterns #2
-
03:25
Android Performance Patterns: Battery Performance 101
-
03:05
Manage your resource's efforts with Assignments view
-
02:33
Building a Responsive UI in Android (Android Development Patterns)
-
08:02
LEGO Fortnite - Where to Find Every Resource
-
04:22
Android Performance Patterns: Understanding VSYNC
-
03:08
Android Performance Patterns: Tool - Memory Monitor
-
03:59
Android Performance Patterns: Invalidations, Layouts, and Performance
-
26:36
Android Design in Action: Navigation Anti-Patterns
-
10:44
Tools and patterns for scalable Android app testing
-
04:47
Android Performance Patterns: Android UI and the GPU
-
04:29
Android Performance Patterns: Understanding Battery Drain on Android
-
02:59
Android Performance Patterns: Understanding Overdraw
Loading...