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


To measure your quality level, pick the best answer for your team and company and write down the count of each of the letters ad. After that, we will do some calculations:

  1. Development process:

a. Waterfall

b. Fake agile

c. Agile

  1. Development cycle:

a. Test last

b. Test at the same time

c. Test first (TDD or maybe BDD with the test defined with behavior)

  1. Team:

a. QA and development teams separated

b. Developers work closely with testing but separate CRs

c. CRs have developers and test experts

  1. Team 2:

a. SDETs do most testing

b. QAs do most testing

c. Developers do most testing

  1. Deployment:

a. Require manual intervention

b. Deployments are tested offline or at off-peak hours

c. Fully built-in CI/CD

  1. Regression:

a. New features can affect old ones

b. New features rarely affect old ones

c. New features are handled by feature tags

  1. Type of...