Book Image

How to Test a Time Machine

By : Noemí Ferrera
Book Image

How to Test a Time Machine

By: Noemí Ferrera

Overview of this book

From simple websites to complex applications, delivering quality is crucial for achieving customer satisfaction. How to Test a Time Machine provides step-by-step explanations of essential concepts and practical examples to show you how you can leverage your company's test architecture from different points in the development life cycle. You'll begin by determining the most effective system for measuring and improving the delivery of quality applications for your company, and then learn about the test pyramid as you explore it in an innovative way. You'll also cover other testing topics, including cloud, AI, and VR for testing. Complete with techniques, patterns, tools, and exercises, this book will help you enhance your understanding of the testing process. Regardless of your current role within development, you can use this book as a guide to learn all about test architecture and automation and become an expert and advocate for quality assurance. By the end of this book, you'll be able to deliver high-quality applications by implementing the best practices and testing methodologies included in the book.
Table of Contents (19 chapters)
Part 1 Getting Started – Understanding Where You Are and Where You Want to Go
Part 2 Changing the Status – Tips for Better Quality
Part 3 Going to the Next Level – New Technologies and Inspiring Stories
Appendix – Self-Assessment

The secret passages – remote execution

On occasions, we want to run our tests in a remote browser rather than locally. Sometimes, we want to run them on a particular port of a machine.

This could be useful for many reasons, one of which is that we want to grant access from a particular IP range to a particular port on a particular server. This way, we could avoid setting tokens, headers, or cookies. It could also help us get a more secure and private connection for our tests, and allow us to open and close the port to run the tests only when needed.

Most of the time, we want to test on a specific device or against a device farm. We could own one or it could be from a third party (they will generally provide the syntax and parameters to test remotely on their devices).

When we use tools such as Appium, under the hood we open a server on a specific port on our local computer (by default, 4723) and by creating a session against it, we are ultimately using a remote browser...