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 (or CAB) is a collective of representatives from different departments within the company who run that company’s formal change management processes. …

More and more companies are beginning to understand that using a staging environment to test features causes more harm than good. Because this process separates …

Continuous integration is the practice of merging the code of all developers on a project and testing for conflicts continuously, as changes are made.

In any complex system, failure is inevitable. Chaos engineering, or chaos testing, embraces this reality, allowing you to introduce failures in a controlled way.

CI/CD is the acronym in software development for the combination of continuous integration (CI) and continuous delivery (CD). It can also be expanded to include …

Client-side testing refers to any type of testing – commonly A/B testing, but also multivariate testing or multi-armed-bandit testing – that occurs in the user’s …

Customer experience (abbreviated CX) is the experience your customers have with your brand. Customer experience metrics are organizational KPIs that help you monitor your customer …

A controlled rollout is a feature rollout with highly granular user targeting. It allows you to release new features gradually, ensuring a good user experience …

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 …

Continuous delivery is the process of systematically keeping code deploy-ready at all times. This shift in release process requires several changes in the operations of …