Test your Cleverbridge setup and integrations

Use test orders to validate your Cleverbridge configuration and connected systems before making a checkout available to customers.

Before you test

Use dedicated test products, configurations, and data whenever possible. Do not enter real customer information in test orders.

Make sure that you know which parts of the workflow you need to verify, such as payments, subscriptions, delivery, customer emails, notifications, CRM processing, and post-purchase experiences.

Generate a test credit card number

1. In the Cleverbridge platform, go to Settings > Users.
2. Open the user who will place the test order.
3. In the General settings, generate or copy the Test credit card number.
4. Save the user if you generated a new number.

Generating a test credit card number requires the appropriate user privilege. If the action is unavailable, contact your Cleverbridge administrator.

Place a test order

1. Open the checkout you want to test.
2. Enter test customer and billing information.
3. Enter the generated test credit card number.
4. Enter any future expiration date and any three-digit security code.
5. Complete the purchase.

The system identifies the completed purchase as a Successful Test Order, which allows you to distinguish it from a real order.

For Purchase Order testing, see How do I generate a test PO?.

Verify the complete workflow

After placing the order, verify the parts of the workflow that apply to your setup:

• The order has the expected status and is identified as a test order.
• The payment result is correct.
• The subscription was created or updated correctly.
• The product, license, or other entitlement was delivered.
• The expected customer emails were generated.
• Notifications reached your connected systems and were processed correctly.
• CRM and other downstream workflows completed as expected.
• The post-purchase experience works correctly.

You can also use controlled test scenarios to review unsuccessful-payment and recovery workflows.

Use dedicated test configurations

To avoid affecting live configurations, create dedicated products, promotions, recommendations, and other items for testing.

The configuration process is the same as for production items. Use a clear naming convention, such as a TEST prefix, to make test items easy to identify. Do not publish links to these items on customer-facing channels.

Review design changes

Test customer-facing design and messaging changes before they are published to production.

When Cleverbridge provides a staging configuration, open the staging link in a browser and review the updated experience without affecting the live checkout. Cleverbridge publishes the changes to production after you approve them.

Production testing guardrails

Follow these guardrails when testing in a production account:

• Use dedicated test setups and data. Use designated products, configurations, and data for testing. Never use real customer information. To make test orders easier to recognize, you can also include Test in an address field.
• Limit testing volume. Do not create more than 200 test orders consecutively or exceed 1,000 active test subscriptions at any time. Contact Cleverbridge before running a scenario that requires a higher volume.
• Maintain data integrity and compliance. Keep test activities isolated from real customers. Avoid triggering real customer emails, notifications, or transactions, and follow applicable data-protection requirements.

warning

Never run automated, performance, load, or stress tests in a production environment.

Did you find this doc useful?