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

Thinking out of the box about the cloud

There could be many other advantages to using cloud computing other than speeding up testing and deployments. For example, we already covered this in Chapter 6, Continuous Testing – CI/CD and Other DevOps Concepts You Should Know. CI (and/or testing) could be performed and installed in the cloud by using runners.

Runner

In CI/CD, a runner is an agent (a program) available in one or more machines that can execute jobs (pieces of code).

Runners can be local or live in the cloud. For this chapter, we are considering mostly the ones in the cloud.

Runners can perform several actions, including setting up a Dockerfile to prepare the runner with the required programs to install and run the app. They can also run the test code, which will call the cloud provider if we are using one. That would be a cloud that is talking to another cloud, about potentially yet another cloud (if your app is serverless):