As the picture showed, CT, CI and CD will work better when they are together. To know how they are achieved by the DevOps server, we need to see each concept of CI, CD, and CT…
Continuous Integration
Continuous Integration (CI) is the process of automating the build and testing of code every time someone commits changes to version control. Many think this is the most critical component to making an effectively agile development team.
Continuous Delivery
Continuous Delivery (CD) is the practice is the practice of streamlining and automating all the processes leading up to deployment. There are a number of steps in CD, such as validating the quality of the build in the previous environment. When done manually these steps can take significant effort and time. However, using cloud technologies and proper orchestration, they can be automated.
Continuous Testing
Continuous Testing (CT), which can also be referred to as Continuous Quality, is the practice of embedding and automating test activities into every “commit”.
CI,CD,CT Pip Line
-
The development environment builds a version from the development branch and runs the Unit testing cases. When success for these cases, we will push code to the testing branch.
-
The testing environment automated run Unit and automation testing case after building finish. But only when these cases passed, the final build will show us a sort of successful building tips. When functional testing is finished in the testing environment, we will push code to the production branch.
-
The testing environment automated run Unit and automation testing case after building finish. But only when these cases passed, the final build will show us a sort of successful building tips. When functional testing is finished in the production environment, we will decide to deliver it to real customers.
More about CI,CD,CT
For more about how the CI,CD,CT work together, you can refer to below video: