01About Club Car
Club Car builds golf cars and personal transportation vehicles. Customers use its website configurator to build and price a vehicle. Behind it sits a CPQ (configure, price, quote) project built on Logik.io.
A configurator is one of the hardest things to test by hand. Every model has its own option rules, some options exclude others, and every combination has to show the right price. Each change to a rule or a price list means walking through the configurator again.
The lesson reaches well beyond golf cars. Any manufacturer that sells configurable products online, from vehicles to industrial equipment, meets the same problem: the configurator is where revenue starts, and it changes more often than almost any other part of the site. Testing it by hand doesn't scale with the number of options.
02Business objectives
- Test the configurator and CPQ flows on every change without a manual walkthrough
- Get coverage in place quickly, without training the project team on another tool
- Increase test coverage and reliability across configurations
- Reduce what QA costs per release
03Testing challenges
Combinations multiply
Models, options, accessories and pricing rules interact, so the number of paths worth testing grows with every new option.
Rules change often
Configuration rules and prices are updated regularly, and each update can break a path that worked yesterday.
No time for a tool rollout
The project team needed tests running straight away, not after weeks of tool training and administration.
Manual passes were slow
Clicking through configurations by hand took QA time away from the rest of the project.
04How they use Robonito
- 1
Demonstrate, don't script
The Club Car team showed the Robonito team the test case they wanted. Robonito's team recorded it and built it out, so nobody at Club Car had to learn a scripting language.
- 2
Hundreds of tests from the start
Using the Robonito Enterprise solution with test-writing support, Club Car was able to record and run hundreds of tests immediately.
- 3
Configurator coverage
Automated tests cover Logik.io configurations and the CPQ configurator, so changes no longer need a manual walkthrough.
05Test scenarios, in plain language
Representative examples of configurator checks, not Club Car's own test list. Each one is typed as written; the agent works through the app and saves the steps.
- Option rulesSelect a model, add an accessory that requires a specific seat kit, and confirm the seat kit is added automatically.
- ExclusionsChoose an option that excludes another and confirm the excluded option is disabled with an explanation.
- PricingBuild a configuration with three accessories and confirm the total matches the sum of the line prices.
- QuoteComplete a configuration, request a quote, and confirm the quote lists every selected option.
- RegressionAfter a price list update, rerun the configuration suite and flag any total that changed.
06Results
Over 70% less testing time
Club Car cut QA testing time by over 70% with Robonito.
Automated configurator testing
Logik.io configurations and the CPQ configurator are tested automatically instead of by hand.
Better coverage and reliability
More configurations are covered, and runs are repeatable on every change.
Lower QA cost
Automation brought significant cost savings, with no extra tool administration for the team.
“With the Robonito Enterprise solution, including test-writing support, we were able to immediately record and run hundreds of tests, without any delay or need for training and administration of yet another tool. All we had to do was demonstrate the desired test case and the Robonito team did the rest.”
07What other teams can take from this
Start with the journeys that earn money
Configurator and quote paths change often and a failure there costs sales directly, so they are the first journeys worth automating.
Buy capacity, not just a tool
When the project team has no time to learn a tool, test-writing support gets coverage running while the team keeps shipping. Robonito's professional services team offers this on enterprise engagements.
Show, don't specify
Demonstrating a test case is faster than writing a specification for it. Recorded flows become tests the team can read and review.
08Frequently asked questions
What is CPQ testing?
CPQ testing checks configure, price, quote software: that option rules, exclusions, pricing and the quote output are right for every valid configuration, and stay right after each rule or price change. Because combinations multiply quickly, teams automate the paths that matter most and rerun them on every change.
How did Club Car cut QA testing time by over 70%?
Club Car used Robonito Enterprise with test-writing support. The team demonstrated the test cases it wanted, Robonito's team built them, and hundreds of tests were recorded and run straight away in place of manual configurator walkthroughs. Club Car reports over 70% less QA testing time.
Can Robonito test Logik.io configurators?
Yes. Club Car's tests cover Logik.io configurations and its CPQ configurator. Robonito tests through the browser the way a user does, so it works with configurators built on web front ends.
Do we have to learn a new tool to get started?
Not necessarily. Tests can be written in plain language or recorded in the Robonito desktop app, and on enterprise engagements Robonito's team can write the tests for you, as it did for Club Car.
Which Robonito plan fits a configurator project?
Web testing is on every plan, including the free plan with 100 test cases a month. Club Car used Robonito Enterprise with test-writing support; for dedicated support and a custom contract, the Custom plan is the match.