Having understood what a CI/CD system entails, let us now review a few test automation strategy considerations for CI/CD. It is much easier to build test automation into CI systems earlier in the project rather than adding it later on. It is essential to understand that all tests cannot be run all the time since that would be an enormous overhead on the CI pipeline as the code base increases. Having the right test automation strategy to utilize CI/CD systems frees up engineers’ capacity that can be utilized in other areas. It goes without saying that building an accurate and reliable software application is possible only by establishing quality right from the lowest building block. Let us start by looking at unit and component tests.

Unit/component tests

Unit tests verify the behavior of the smallest blocks of code, usually a single class or an object, whereas component tests exercise larger blocks of code involving multiple classes...