CASE STUDY
Leading Electric Vehicle Manufacturer
Unifying Digital Commerce, Salesforce, SAP, and Connected-Vehicle Validation with AI-Powered Test Automation.
End-to-end automation with 78% coverage, 70% faster regression, and 80%+ test asset reuse
Industry: Automotive and Electric VehiclesCompany Size: 5,000+
Client Intro
The client is a US-based electric vehicle manufacturer known for premium, software-defined vehicles, direct-to-consumer digital sales, connected services, and advanced driver-assistance technology. Its customer journey extends from online vehicle discovery and configuration to reservation, financing, order management, inventory allocation, delivery, mobile services, and post-purchase support.
This experience depends on a complex digital ecosystem. The public retail platform manages vehicle configuration and online purchases, Salesforce supports customer and sales operations, while SAP manages inventory and core enterprise processes. Mobile-responsive experiences, backend APIs, payment services, connected-vehicle platforms, and embedded software services add further dependencies.
The organization had already automated portions of its public website using Selenium and Playwright. However, these frameworks could not provide stable, maintainable coverage across Salesforce and SAP. The client selected ACCELQ to replace fragmented automation with a unified platform capable of validating complete customer and enterprise journeys.
Business Objectives
The client wanted to establish one automation experience across its online retail platform, Salesforce, SAP, APIs, and mobile-responsive channels. Its primary objective was to validate the complete vehicle-buying journey—from configuring a vehicle online to creating the customer record, confirming inventory, processing the order, and preparing the vehicle for delivery.
The organization also wanted to reduce the maintenance created by quarterly Salesforce and SAP updates, standardize automation across cross-functional teams, and trigger relevant tests automatically through Jenkins and Azure DevOps whenever the retail platform changed.
As a software-defined vehicle manufacturer, the client also needed stronger validation at the boundary between customer-facing applications and connected-vehicle services. This included vehicle-account association, mobile application workflows, feature entitlements, software-version compatibility, over-the-air update orchestration, and service status visibility.
Automation Challenges:
-
Fragmented Automation Across the Technology Stack
Web, Salesforce, SAP, mobile, and integration teams used different tools, frameworks, and reporting practices. Selenium and Playwright supported the public website but required separate solutions for packaged applications. This prevented the QA organization from executing or governing the complete vehicle-purchase journey as one business process.
-
Brittle Salesforce and SAP Automation
Dynamic Salesforce components, SAP interface changes, generated identifiers, asynchronous behavior, and quarterly vendor releases repeatedly broke open-source scripts. Teams spent significant time updating locators and framework code before they could assess whether the underlying business process still worked.
-
Complex Online Vehicle-Buying Journey
A single customer journey could span vehicle configuration, pricing, reservation, financing, trade-in details, Salesforce lead and opportunity creation, SAP inventory checks, order submission, payment confirmation, delivery scheduling, and customer notifications. Validating individual systems independently left critical integration gaps undetected.
-
Highly Variable Product Configuration
Automation had to accommodate vehicle models, trims, exterior and interior combinations, wheel options, regional availability, pricing, taxes, financing conditions, inventory states, and delivery locations. Duplicating tests for every configuration would have created an unmanageable regression suite.
-
CI/CD Execution Was Not Business-Risk Aware
Changes to the retail site were deployed through Jenkins and Azure DevOps, but automated validation was not consistently extended into Salesforce and SAP. A successful web build did not confirm that customer, inventory, order, and fulfillment records were correctly processed downstream.
-
Long regression cycles before product releases
Manual regression for SCADA, Spectrum Power, and Opcenter workflows consumed 10–12 business days across priority modules. This delayed release readiness and increased pressure on QA teams during release windows.
-
Connected-Vehicle and Embedded-System Dependencies
Post-delivery experiences—including mobile access, vehicle pairing, charging, feature entitlements, and OTA updates—depended on reliable communication across customer apps, cloud services, and in-vehicle systems. While safety-critical driver-assistance functions required specialized embedded testing, their connected digital workflows still needed end-to-end release validation.
-
Limited End-to-End Failure Visibility
When an order or connected-service workflow failed, teams had to investigate multiple systems to determine whether the cause was the website, Salesforce, SAP, an API, invalid test data, or an environment issue. Disconnected reporting made root-cause analysis slow and increased release risk.
Honestly, I was surprised how easy it was. We’ve tried several tools over the years, and each one was great at a specific vendor app or technology—but only that one thing. ACCELQ is the first that lets us run true end-to-end in a codeless format, without giving up the governance, control, and power you’d expect from a traditional framework.
- Staff Quality Engineer, Automotive and EV Manufacturer
Benefits
ACCELQ helped the client shift from fragmented manual validation to a unified, scalable automation model designed around real business processes and operational workflows.
Unified Web, Salesforce, and SAP Automation
- ACCELQ unified vehicle configuration, Salesforce customer records, SAP inventory, order processing, and API validation within one end-to-end flow.
Faster Build-Out with Pre-Built Assets
- Release-aligned Salesforce and SAP components accelerated automation development while eliminating the need to maintain extensive locator libraries.
Stable Automation Through Vendor Updates
- AI-powered self-healing absorbed application changes and quarterly vendor updates, reducing automation maintenance effort by an estimated 60%.
Reusable Vehicle-Buying Components
- Modular components supported different models, trims, regions, pricing rules, and inventory states while achieving more than 80% reuse.
Automated Validation Through CI/CD
- Integration with Jenkins and Azure DevOps triggered targeted and regression tests after deployments, providing faster feedback on downstream impacts.
Broader Digital Experience Coverage
- Reusable tests validated desktop, mobile-responsive, cross-browser, API, and accessibility experiences without requiring separate automation frameworks.
Connected-Vehicle Workflow Assurance
- ACCELQ validated vehicle pairing, feature entitlements, OTA status, mobile workflows, backend APIs, and customer-visible service information.
Embedded-System Integration
- Specialized systems tested safety-critical vehicle functions, while ACCELQ provided traceability across the surrounding digital and enterprise workflows.
Faster Diagnosis and Centralized Governance
- Centralized results, logs, screenshots, and execution evidence simplified failure analysis and gave teams a consistent view of release readiness.
Faster Releases at Higher Quality
Regression across web, Salesforce, and SAP reduced from ten business days to one day.
Significant Cost & Effort Reduction
AI-powered self-healing reduced maintenance caused by UI changes and packaged-app updates.
Business Process Focused
Automation covered the complete journey from vehicle configuration through ordering and delivery.
Technical Excellence with Sustainable Benefit
Reusable assets scaled across vehicle models, regions, pricing conditions, and connected services.
