The way businesses handle their revenue processes is evolving as a result of Salesforce's shift from CPQ to RLM under the Revenue Cloud umbrella. QA teams are under pressure, though, to modify their current test automation suites to fit the new architecture. With the changing UI, API, and system architecture, legacy CPQ test automation frameworks created with Selenium, Playwright, or Copado CRT are now incompatible. In this article, we will look at how to successfully refactor and move your Salesforce CPQ test cases to RLM. By incorporating AI-powered QA techniques, we will show you how to streamline testing, reduce manual effort, and maintain comprehensive test coverage to ensure smoother transitions and faster go-live readiness.

What are the Common Challenges in Migrating CPQ Test Suites to RLM?

Enterprises that have already built a robust test automation regression suite for Salesforce CPQ, using tools like Selenium, Tosca, Playwright, or Copado CRT, are now facing a critical dilemma that these scripts are no longer directly usable in Revenue Lifecycle Management (RLM), which presents a significant challenge. To understand the scope of these challenges and how they impact your test automation efforts, let's take a closer look at the key differences between Salesforce CPQ and Salesforce RLM, and the specific automation adjustments required to migrate your test suites successfully.

Category

Salesforce CPQ

Salesforce RLM (Revenue Cloud)

QA Automation Impact

UI Framework

Classic Aura-based components.

Lightning Web Components (LWC).

Requires locator updates, support for shadow DOM, and modern UI testing tools.

User Navigation

Linear, step-driven flows.

Modular, tab-based interface with dynamic rendering.

User journeys need to be redefined and re-sequenced.

API Availability

Legacy CPQ-specific APIs.

New RLM APIs with changed endpoints and schemas.

Test scripts must update endpoints, payloads, and validation rules.

Component Structure

Monolithic CPQ pages.

Componentized revenue flows (e.g., Product Configurator, Pricing Engine).

Enables modular test case design and reuse.

Test Data Schema

Custom CPQ data models.

Updated objects and relationships in RLM.

Requires rework of test data factories and test coverage mapping.

Automation Reusability

Limited, tightly coupled to the CPQ architecture.

Moderate to high, if refactored using AI-based selectors and APIs.

Reuse is possible with intelligent automation refactoring.

CI/CD Integration

Basic CI/CD support, not optimized for DevOps.

Designed for modern DevOps with APIs, metadata tracking, and GitOps readiness.

Encourages integration with GitHub Actions, Jenkins, and Copado pipelines.

Visual Validation

Not essential—UI changes are infrequent.

Essential—UI elements shift frequently with dynamic components.

Visual AI testing and dynamic wait strategies are becoming increasingly important.

Self-Healing Support

Minimal support unless using advanced tools.

Works well with modern tools like Copado CRT, Testim, Playwright, and AI plugins.

Enhances resilience of automation with AI-based selectors and test maintenance routines.

The migration challenges typically fall into two major categories:

  1. UI / Functional Changes
  • RLM introduces a modernized UI with Lightning Web Components (LWC), new navigation patterns, and updated user journeys.
  • UI redesigns disrupt existing locators, page models, and test flows.
  • Automation frameworks need to be refactored to align with RLM’s dynamic, component front-end.
  1. API Changes
  • Many CPQ APIs are deprecated or restructured in RLM.
  • Test cases that validate workflows (like Quote-to-Cash, Pricing, and Amendments) using CPQ endpoints will fail in RLM.

How AI Can Streamline the Migration Process

Migrating your existing CPQ automation to Salesforce Revenue Cloud doesn't have to be a daunting task. The entire migration process can be made simpler by integrating AI and Natural Language Processing (NLP). AI can seamlessly replace API calls in your current test cases and automatically map legacy CPQ APIs to their new RLM counterparts. This reduces manual effort, ensures greater consistency, and enables automation reuse, making the migration process smoother and more efficient.

With AI-driven solutions, QA teams can more effectively evaluate, redesign, and migrate their test assets for Salesforce Revenue Cloud while minimizing risk and maximizing reuse.

Let’s break this process down into two key phases:

Phase 1: Assessment and Planning

In the first phase, the focus is on gaining a thorough understanding of the existing CPQ test cases and the changes required to adapt them for RLM.

Activities:

  • Catalog existing CPQ test cases across all layers: UI, API, and integration.
  • Prioritize business-critical workflows such as Quote Creation, Pricing, and Approvals.
  • Analyze the Revenue Cloud architecture and compare it with the existing CPQ system.
  • Collaborate with business stakeholders to assess functional and process-level changes.

Key Deliverables:

  • Gap Analysis Report
  • Feature Comparison Matrix
  • Stakeholder Sign-Off

Phase 2: Refactoring and Design Alignment

Once the assessment is complete, the next phase focuses on refactoring the test automation assets to align with the Revenue Cloud architecture. Here, AI plays a critical role in making automation changes more quickly and effectively.

Activities:

  • Modification to UI Automation:
    • Update locators for LWC (using data-test id or shadow DOM-aware tools).
    • Introduce dynamic waits and visual validations using tools like Playwright or Copado CRT.
  • Workflow Adjustments:
    • Redefine user journeys based on the new Revenue Cloud UX.
    • Automate modular components (e.g., Product Selector, Quote Summary).
  • API Updates:
    • Map legacy CPQ APIs to the new RLM endpoints.
    • Validate contract/schema changes.

Key Deliverables:

  • Updated Regression Pack.
  • New UI/API Automation Framework Designs.
  • Locator and Wait Strategy Document.

UI Automation

API Test Updates

Update locators for LWC and shadow DOM.

Map CPQ endpoints to RLM APIs.

Use AI to detect element changes.

Validate payload/schema with Swagger/OpenAPI.

Introduce visual testing and dynamic waits.

Auto-update request headers, methods, and parameters.

Modularize test cases based on UX components.

Generate new test cases for additional flows.

Tools: Playwright, Copado CRT, Testim, GPT.

Postman, RestAssured, and OpenAPI diff tools.

Output: Refactored Automation Frameworks, Updated Test Modules, and Locator Strategy Document.

 

How Can Jade Global Help You Transform Your Salesforce Test Automation?

With a wealth of expertise in Salesforce QA transformations, Jade Global uses AI-driven test migration frameworks to expedite the procedure. We offer:

  • Ready-to-use LWC-compatible automation libraries.
  • Domain-specific accelerators for Quote-to-Cash processes.
  • Proven experience in guiding clients through Salesforce test migrations with minimal risk and maximum reuse.

With our AI-powered solutions, your Salesforce test automation transformation is not only faster but more reliable, ensuring greater consistency and scalability as you migrate to Revenue Cloud.

For a clear, step-by-step roadmap from Salesforce experts, check out our ebook!

About the Author

Deepa Joshi

Deepa Joshi

Global Delivery Head - QA

Deepa is a seasoned IT professional with 24+ years of experience in QA Delivery Management, including expertise in software development, maintenance, and independent QA practices across various industries, including, retail , Life Sciences , Hitech, Energy utilities and Services.

How Can We Help You?

document.addEventListener("DOMContentLoaded", function() { const lightbox = GLightbox({ selector: '.glightbox2' }); });