Describing the App with Screen Objects
Let’s think through what we have so far. UI Automation provides a scripting interface to the application through a set of objects representing the window, controls, and device. We act on these objects with events, check the results on the screen, and log errors if they aren’t what we expect.
Our test steps can become very verbose. The test’s meaning gets clouded by complicated lookups and assertions. We need a way to hide the unnecessary stuff.
Because we are dealing with mobile user interfaces, we can break our problem up into “screens” that represent the different cognitive states of the user. In our vernacular, a screen may encompass the whole physical screen, or it could represent a modal view or ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access