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

Types of continuous tests

From Chapter 2, The Secret Passages of the Test Pyramid – The Base of the Pyramid, to Chapter 4, The Secret Passages of the Test Pyramid – The Top of the Pyramid, we explored different types of testing in the test pyramid. In this section, we will see how and where these (and other tests) should be handled through the different steps of our pipeline system, continuously executing them to ensure the high quality of our deployment system.

Unit tests/code review testing

Continuing the example of Figure 6.1, we can commit a feature branch at any time. When we are happy with the contents of the feature branch, ideally after some testing (such as unit tests and code reviews) has taken place, we can merge it to the next branch, including the main trunk.

The test expert should configure the coverage and verify it. We can also create tools to check and ensure the quality of the code being committed before undergoing a code merge.

For more...