In this chapter we covered all the alternatives we have to expose our application and its tests to a wide range of conditions and configurations, ranging from different screen sizes, the availability of devices such as cameras or keyboards, to simulating real life network conditions to detect problems in our application.
We also analyzed all of the options we have to be able to control emulators remotely when they are detached from its windows. This prepares the foundation for Continuous Integration that we will be visiting in Chapter 8, Continuous Integration, and relies on the ability to automatically run all the test suites and having the ability to configure, start, and stop the emulator will be necessary.
At the end, some scripting alternatives were introduced and examples to get you started were provided.
The next chapter will introduce Behavior Driven Development—a technique that makes use of a common vocabulary to express the tests permitting the inclusion of business people...