Continuous...

Continuous Delivery

Sw development practice in which you build software in such a way that it can be released to production at any time.

You’re doing continuous delivery when:

• Focus on quality of working software.

• Your software is deployable throughout its lifecycle.

• Your team prioritizes keeping the software deployable over working on new features.

• Anybody can get fast, automated feedback on the production readiness.

Continuous Deployment/release

Every change goes through the pipeline and automatically gets put into production.

Focus on speed and agility to deploy to production.

Continuous Integration

Automatically integrating, building, and testing code within the development environment.

Pre-delivery steps.

Continuous feedback

Errors are easier to detect in an earlier stage, near the point where they have been introduced:

• The detection mechanism of such bugs becomes simpler because the natural step in diagnosing the problem is to check what was the latest submitted change. Problems followed by atomic commits are easiest to correct than to fix several problems at once, after bulk commits.

There must be an effective mechanism that automatically informs programmers, testers, database administrators and managers about the status of the build.

Continuous testing

Quality checks at all system levels and involve all individuals, not just the elements of the QA team.

Most of the tests can be automated and should be run in the CI pipeline to be carried out repeatedly:

• Unit testing, integration testing, regression testing, system testing, load and performance testing, etc.

Build tools can take a crucial role on automating tests.