Tag: c

Continuous deployment is the practice of automatically promoting code changes to prod after they pass all automated tests in a continuous delivery pipeline.

A change advisory board is a collective of representatives from different departments within a company who runs formal change management processes.

A way to avoid the issues caused by configuration drift is to set up feature flags to test your code in production safely.

Continuous integration happens when you automate the process of integrating your code to master to ensure there are no conflicts.

Chaos engineering, also known as chaos testing, provides a method and tool-set to deliberately introduce failures and outages in a system.

CI/CD is the acronym in software development for the combination of continuous integration (CI) and continuous delivery (CD).

Client-side testing refers to any type of testing, commonly A/B testing, multivariate testing or multi-armed-bandit testing occurring in the user’s browser.

Today, we’ll discuss some of the most commonly-used customer experience metrics and explain the benefits and drawbacks of each.

A controlled rollout allows the release of new features gradually, ensuring a good user experience before releasing them to larger groups.

A canary deployment, or canary release, is a deployment pattern that allows you to roll out new code/features to a subset of users as an initial test.

When implementing continuous delivery, shifting toward purpose-built continuous delivery tools is critical. Here, we discuss the most popular CD tools.