ab-testing-implementation

To validate A/B test implementations, run the compliance script check-ab-testing-compliance.sh, which checks ab_tests payloads, variant configs, and useABTest usage against the canonical standards defined in docs/ab-testing.md.

The canonical source of truth for A/B testing standards in MetaMask Mobile is the docs/ab-testing.md file, which defines workflow rules, analytics rules, risk-based testing policy, and compliance commands for all A/B test implementations.

Adding variant configs and useABTest hooks safely requires following the risk-aware workflow and testing policies in docs/ab-testing.md, then running the compliance validation script to ensure analytics payloads and configurations meet repository standards.

Yes, you must update analytics payloads when modifying A/B tests in MetaMask Mobile, as the compliance script validates analytics payloads alongside ab_tests payloads and variant configs to ensure consistent, compliant tracking across all test variants.

A/B testing compliance rules for MetaMask Mobile require following the workflow, analytics rules, risk-based testing policy, required response sections, and compliance commands defined in docs/ab-testing.md, validated by the check-ab-testing-compliance.sh script.