shift-right-testing

name	shift-right-testing
description	Testing in production with feature flags, canary deployments, synthetic monitoring, and chaos engineering. Use when implementing production observability or progressive delivery.
category	testing-methodologies
priority	high
tokenEstimate	1000
agents	["qe-production-intelligence","qe-chaos-engineer","qe-performance-tester","qe-quality-analyzer"]
implementation_status	optimized
optimization_version	1
last_optimized	"2025-12-02T00:00:00.000Z"
dependencies	[]
quick_reference_card	true
tags	["shift-right","production-testing","canary","feature-flags","chaos-engineering","monitoring"]
trust_tier	3
validation	{"schema_path":"schemas/output.json","validator_path":"scripts/validate-config.json","eval_path":"evals/shift-right-testing.yaml"}

Shift-Right Testing

<default_to_action> When testing in production or implementing progressive delivery:

1. IMPLEMENT feature flags for progressive rollout (1% → 10% → 50% → 100%)
2. DEPLOY with canary releases (compare metrics before full rollout)
3. MONITOR with synthetic tests (proactive) + RUM (reactive)
4. INJECT failures with chaos engineering (build resilience)
5. ANALYZE production data to improve pre-production testing

Quick Shift-Right Techniques:

• Feature flags → Control who sees what, instant rollback
• Canary deployment → 5% traffic, compare error rates
• Synthetic monitoring → Simulate users 24/7, catch issues before users
• Chaos engineering → Netflix-style failure injection
• RUM (Real User Monitoring) → Actual user experience data

Critical Success Factors:

• Production is the ultimate test environment
• Ship fast with safety nets, not slow with certainty
• Use production data to improve shift-left testing </default_to_action>

Quick Reference Card

When to Use

• Progressive feature rollouts
• Production reliability validation
• Performance monitoring at scale
• Learning from real user behavior

Shift-Right Techniques

Technique	Purpose	When
Feature Flags	Controlled rollout	Every feature
Canary	Compare new vs old	Every deployment
Synthetic Monitoring	Proactive detection	24/7
RUM	Real user metrics	Always on
Chaos Engineering	Resilience validation	Regularly
A/B Testing	User behavior validation	Feature decisions

Progressive Rollout Pattern

1% → 10% → 25% → 50% → 100%
↓      ↓      ↓      ↓
Check  Check  Check  Monitor

Key Metrics to Monitor

Metric	SLO Target	Alert Threshold
Error rate	< 0.1%	> 1%