Have you ever wondered how Appium works under the covers? Do you get frustrated with locators not locating, app screens not loading, or test behaving inconsistently from one run to the next? Appium is an attempt to unify thousands of disparate elements across a wide spectrum of challenges into a single, common interface that works seamlessly across all the major mobile and desktop OSs - and yet only a handful of volunteers work to maintain this gigantic effort. If you would like to enhance your own Appium experience while contributing back to the software that has defined so many of our careers, come to this workshop. We'll dissect the different elements of Appium, dive into its internals, learn how it was built and how to make changes to it, and even write a unit test you can contribute on the same day!

Android's Espresso framework was created as a "gray-box" testing framework, "gray-box" meaning that it's an 
automated UI testing framework ("black-box") but it has access to the internals of the application 
("white-box"). Allowing access to the internals of the application-under-test opens up many new testing 
possibilities that weren't possible with UiAutomator2 (with some risks).

Here are the four new possibilities I would like to discuss (with coding examples)

* Access to internal app code
* Less flakiness thanks to "IdlingResource". No need for 'waits' and 'delays' for UI.
* Navigate WebViews using Espresso WebAtoms (this feature is in progress, will be ready well before June)
* Find elements off-screen using Espresso's DataMatchers (this feature is in progress, will be ready well before June)