CPQ SPYDR
Accelerate CPQ Testing & Super Charge Efficiencies
Features of CPQ SPYDR
- ● Multiple line verification
-
● Ability to test different types of bundles and standalone products
in one script - ● Ability to search pre-existing test scripts and re-run
- ● Easily create scripts from excel based templates
- ● Automates bundle configuration testing
- ● Price rule verification
- ● Block pricing verification
Benefits of CPQ SPYDR
AUTOMATED
Automated testing software to help Salesforce CPQ customers test bundles and standalone products efficiently and accurately
COST SAVING
Reduces QA effort and cost to a fraction of manual testing effort and cost
TIME SAVING
Allows customers to test and re-test all scenarios throughout the testing phase as many times as needed by reducing the project timeline and cost
BETTER SALES
Helps sell the correct product configuration and give proper quotes.
Why Automated?
Manual Testing Process
v/s
Automated Testing Process
Create Test Scripts
Excute Testing
- Launch Application
- Create Quotes → Configure Bundle →Save to Quote Lines to Validate Price and Configuration
- Document Results in Word/Excel
- Average Time Taken: 5 minutes/script
Time Taken for Testing
- 30 Bundles
- 30 Test Case
QA Testing is Inefficient
- QA will only re-execute that test script against which a bug exists. In such cases cascading impact always goes un-noticed
- Sample testing is done across models if global fixes are applied
- Only sample testing is done when data is migrated between instances
- Regressions Testing is only sampled across models
Create Test Scripts
Excute Testing
- Upload Test Script(s) to CPQ SPYDR App
- Click on Execute Button to Validate Results
- Average Time Taken: 0.5 second/script
Time Taken for Testing
- 30 Bundles
- 30 Test Case
- 99% Efficient Improvement
QA Testing is Accurate
- 100% test cases are executed/model as many times as needed after bug fixes
- 100% test cases are executed/model in case of global fixes
- 100% test cases are executed/model in case of data migrations
- 100% Regression Testing
Sample scenario of a very low to medium complexity test case in CPQ. Some test cases could be huge and complex in certain industries and
might take much longer than indicated above.
What Does It Mean to Your Organization's
Topline and Bottomline
Be sure that your configuration and pricing rules did not break with three Salesforce releases a year
3-5%
If you can reduce the returns by atleast
3-5% from bad configuration
20%
Reduce your go-to-market time,
product & pricing changes, & CPQ
release testing changes by 20%
5-10%
Improve you CPQ pricing accuracy
by an additional 5-10%
Improve overall go-to-market time & ROI
1
%
Reduced QA Effort
1
%
Reduced Implementation Cost
1
%