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

What is inside the base of the pyramid?

The base of the pyramid contains those tests that are closest to the development of the feature. Although there are some discrepancies around this claim, it is usually where most tests should take place. The reason is that the earlier the issues are found, the cheaper it is to fix them. In this case, the monetary value of finding an issue is measured by the amount of time spent figuring out why it has happened (debugging) plus the amount of time spent fixing it and the context switch needed if the developer has moved on to a different task.

Tests closest to the feature’s development are sometimes referred to as “structural.” In the 2D test pyramid (or triangle), the tests that are located here are unit tests.

Most developers include testing tools and processes in their development, although, interestingly, some of the tools and processes are not even considered as part of quality by them. Some developers claim that...