Architecting a system
We have seen some of the options we have whe building automation for our system, what is left is how to put our system together, as this book is about test architecture, not only its components.
There are many ways we could automate our system and many choices we could make. A good system architecture will allow you to replace components with others when needed, in such a way that the system will still work.
For example, in this chapter, we have seen how to call different programs within another program in the testReporting.py
code. However, in Chapter 6, Continuous Testing – CI/CD and Other DevOps Concepts You Should Know, we did something similar as a part of a CI/CD system in the logAnalizer.py
code. How shall we decide between the two ways?
For simple applications or a quick turnaround, we could go for the solution in this chapter. However, if some of the programs that are called with subprocesses were to break (or someone deliberately breaks...