You're reading from How to Test a Time Machine A practical guide to test architecture and automation

Product type Paperback

Published in Mar 2023

Publisher Packt

ISBN-13 9781801817028

Length 384 pages

Edition 1st Edition

Concepts

Test Driven Development

Author (1):

Noemí Ferrera

View More author details

Table of Contents (19) Chapters

Preface

1. Part 1 Getting Started – Understanding Where You Are and Where You Want to Go

2. Chapter 1: Introduction – Finding Your QA Level FREE CHAPTER

3. Chapter 2: The Secret Passages of the Test Pyramid – The Base of the Pyramid

4. Chapter 3: The Secret Passages of the Test Pyramid – the Middle of the Pyramid

5. Chapter 4: The Secret Passages of the Test Pyramid – the Top of the Pyramid

6. Part 2 Changing the Status – Tips for Better Quality

7. Chapter 5: Testing Automation Patterns

8. Chapter 6: Continuous Testing – CI/CD and Other DevOps Concepts You Should Know

9. Chapter 7: Mathematics and Algorithms in Testing

10. Part 3 Going to the Next Level – New Technologies and Inspiring Stories

11. Chapter 8: Artificial Intelligence is the New Intelligence

12. Chapter 9: Having Your Head up in the Clouds

13. Chapter 10: Traveling Across Realities

14. Chapter 11: How to Test a Time Machine (and Other Hard-to-Test Applications)

15. Chapter 12: Taking Your Testing to the Next Level

16. Index

Why subscribe?

17. Other Books You May Enjoy

Appendix – Self-Assessment

Assessment

CI/CD and other DevOps concepts that you should know

In this section, we will cover some DevOps concepts you should be aware of and understand in order to be fully involved with and committed to CI/CD systems. Feel free to skip the blocks you are already familiar with.

Pipelines

A pipeline (also known as a deployment pipeline) is the way we organize our deployment system. Each of the steps in our pipeline is matched with an environment that we use to configure the system under development, merge the different versions, and test them.

Branches

When developing an application, it is convenient to keep different versions of the code, especially when such code is built by different developers at the same time. Each version could correspond with a feature or with a state of the application. The reason that these are called branches is from the analogy of a tree, where the main trunk can split into different branches.

A typical design of branches can look as shown in Figure...