What is continuous testing?
In order to understand CT and how to achieve it, we must first define CI/CD and other core concepts.
Continuous integration
When several people are working on the same piece of code, issues between the different versions of the code can easily appear. We need a system to keep all the code versions together. The place where code is kept is called a code repository.
CI consists of frequently integrating and merging feature code into a shared repository, preferably several times a day. Each integration can then be verified by an automated build and automated tests, which will be part of CT. This is done from within the repository or the different environments set up in the deployment pipeline. The goal is to ensure there are no integration issues and to identify any problems early.
As we evaluate the state of the code after each integration, we can locate and fix integration problems individually. If we do not use this technique, it is harder to...
