Testing in staging alone doesn’t give teams the confidence they need to move fast and reduce cycle times. No matter how much you invest there, it will never have the same data, activity, and signals that production has.

Instead, shift your focus towards making a wide range of testing in production strategies safe, efficient, and well-understood by your teams. Testing directly in production gives them a clearer understanding of how a change behaves, whether in infrastructure, the data layer, the front end, or anywhere in between. Pairing this with the ability to limit who sees a change in production means a superior developer experience and a better user experience.

What You'll Learn:

Specific strategies we’ve used to test in production safely with feature flags

Tap compare testing to validate functional parity of new services before cutting away from old Mirroring/shadowing to exercise new services at full scale with low risk

Canaries to gradually expose real users and learn before full rollout

Config testing to explore optimal combinations of settings

Alpha and beta programs to safely test in production

How feature flags + data change the risk/reward balance in your favor, using real-time metrics, monitors, and alerts to quickly identify and rollback features having a negative impact

This session is presented by Split.