CI is the process of running unit tests and automated interface tests on every code change (typically each commit). This is great because it provides near-constant feedback to your developers, so that if they break something during development they know about it immediately and can fix it before it gets further down the line to a review phase.
Developers upload the smallest changes in code to the central repository, and whenever the code is updated, we have a series of tests performed to ensure the top-quality of each code segment.
The fundamental idea of CD is that releasing small chunks of isolated code is the least risky way to deploy since, to put it simply, fewer code changes means less risk of unforeseen bugs and easier debugging if bugs do appear.
Continuous delivery allows the release of new iterations on a constant basis. It enables us to react to bugs and issues as soon as they are detected.
The role of QA in continuous delivery is to accelerate deployment, rather than hold it back. Aside from the fact that it’s cheaper to do QA continuously, it’s also much faster. Continuous testing creates a “safety net” that increases dev confidence in making changes and shipping updates. There’s a much less prominent risk of shipping code, because if something breaks they can rely on QA to catch it.
Try QA assurance with Mad Devs and don’t worry at all about your product!
