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 – making your UI tests more efficient with API calls

The goal of every test is to be as small and specific as possible. That way, by taking a glance at the test results, you should be able to tell what went wrong. Making debugging easier is indispensable and valuable, especially as applications grow.

When writing tests, the first question to ask is “what am I trying to test?”. The second one is “why?”. As obvious as it might sound, these questions are imperative to write powerful and simple tests. At times, we end up testing things that do not correspond to our application’s behavior or end up writing a long succession of events to reach the small part that we want to test.

To help with the question of “why am I trying to test” and avoid repetition across tests, we can leverage the use of API calls. While using a UI for testing is a great way of simulating the actual behavior of the users, certain actions...