Espresso: How work? — Hamcrest Matchers dig through the view hierarchy — Only considers the portions of the view immediately visible to the user — Can enter text, tap things, scroll, swipe out of the box
Espresso: How work? — Hamcrest Matchers dig through the view hierarchy — Only considers the portions of the view immediately visible to the user — Can enter text, tap things, scroll, swipe out of the box — Create your own actions
UI Testing Best Practices — Don't navigate through your entire UI every single time. — Use class and instance Before/After methods — Create a test class for each piece of your UI
UI Testing Best Practices — Don't navigate through your entire UI every single time. — Use class and instance Before/After methods — Create a test class for each piece of your UI — If there are things you can test without the UI, test them without the UI.
Other Tips for UI Testing — Make a mock flavor, and test on it — Feed your networking stack mock data (Mocktrofit) — Compare R.string string resources to what's on screen.
Other Tips for UI Testing — Make a mock flavor, and test on it — Feed your networking stack mock data (Mocktrofit) — Compare R.string string resources to what's on screen. — Remember when you need to scroll!
Other Tips for UI Testing — Make a mock flavor, and test on it — Feed your networking stack mock data (Mocktrofit) — Compare R.string string resources to what's on screen. — Remember when you need to scroll! — Get to a piece of your UI that's buried without having to tap 800 buttons yourself
NOTE: If You're Using JUnit4... You should Bookmark Jake Wharton's gist for accessing the activity: https://gist.github.com/ JakeWharton/ 1c2f2cadab2ddd97f9fb