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)
1
Part 1 Getting Started – Understanding Where You Are and Where You Want to Go
6
Part 2 Changing the Status – Tips for Better Quality
10
Part 3 Going to the Next Level – New Technologies and Inspiring Stories
Appendix – Self-Assessment

Continuous Testing – CI/CD and Other DevOps Concepts You Should Know

In the last chapter, we explored different ways of designing user interface (UI) test automation frameworks. This is found at the top of the pyramid that was introduced in the previous three chapters. The topic of this chapter might seem as though it lands at the bottom of that pyramid, so people working in testing tend to forget about it. However, it is crucial for any system to have the right number of tests that confirm the quality of the code changes that are being implemented and delivered to the user. Continuous testing (CT) forces the different tests of the pyramid to be run automatically and continuously across all of the deployment phases of the application.

Deciding the approach for this chapter was a tricky task. On the one hand, many concepts could benefit from exact examples. On the other hand, each of the concepts could be written in a different way depending on the tools used. Our advice is...