How would you test a CPQ configuration before deploying to production?

CPQ configuration testing requires a structured approach:

1. Sandbox-First Development: All CPQ configuration (products, rules, templates, package settings) should be built and tested in a full or partial sandbox before promotion.
2. Unit Testing Pricing Scenarios: Create test quotes covering every pricing scenario — each discount schedule tier, each price rule condition, each product rule action. Verify the pricing waterfall at each step.
3. Bundle Configuration Testing: Test all option combinations including required options, constraints (requires/excludes), feature min/max, and selection rules. Verify edge cases like zero quantity and maximum quantity.
4. End-to-End Lifecycle Testing: Create a quote → contract it → generate an amendment → generate a renewal. Verify subscription records, twin field mapping, and delta quantity calculations.
5. Output Document Testing: Generate PDFs for all template variations and record types; check conditional sections, line column formatting, and grouping.
6. Permission Testing: Test as a CPQ User (not Admin) to catch FLS and permission issues.
7. Deployment: Use Change Sets, Gearset, or Copado to move configuration metadata; note that CPQ managed package records (Price Rules, Product Rules, Discount Schedules) are data — use Data Loader or a data migration tool, not Change Sets, to move them between environments.