Test and use cases
Tap into these use cases when developing and testing the Commerce API and your commerce connector.
Last updated
Was this helpful?
Tap into these use cases when developing and testing the Commerce API and your commerce connector.
Last updated
Was this helpful?
Before and after any production deployment, we recommend running regression tests similar to those outlined below on your site. We suggest using these tests as a baseline. You can customize the test cases based on your implementation. As required, include additional tests such as reviewing the logged API response codes, browser compatibility, domain or TLS security, JavaScript errors, etc.
Since "live changes" do not allow testing in a DESIGN or TEST mode, we recommend that you integrate your Stage or Test systems with Digital River's Client Test Environment (CTE) whenever possible. It will help facilitate safe end-to-end testing of all changes before you deploy them to production.
The Client Test Environment (CTE) is a dedicated testing platform provided by Digital River that allows businesses to safely conduct end-to-end testing of all changes in a simulated environment before deploying them to the production environment. It includes testing API integrations, payment processing, and user interface interactions without affecting live data or operations.
Integrating with the CTE is highly recommended for staging or testing systems, as it facilitates a secure and controlled setting for developers and QA teams to:
Verify API response codes and functionality.
Test the application of discounts and promo codes.
Confirm the handling of multiple currencies and locales.
Ensure the correct operation of the cart and checkout processes.
Check browser compatibility and responsiveness.
Assess any customizations or integrations specific to the client's setup.
By using the CTE, teams can identify and address issues before they impact the end-user experience, thereby enhancing the quality and reliability of the eCommerce platform. See for more information on the CTE.
On pre-cart pages, ensure that the expected products, currency, pricing, and discounts appear on the Home page, Category pages, and Product pages. If your store supports multiple countries and regions, verify that locale language and currency changes as expected by country and region.
Confirm the product IDs, category IDs, and locale parameters are passed as expected.
Confirm the API responses are consumed as expected.
Add two or three products to a cart:
Adjust the product quantities and delete one line item from the cart.
[Required for account creation.] Create a new shopper and sign in as the shopper.
Submit the payment information and billing address from the Payment or Billing Address page. We recommend manually entering the address without using the Form Filler and verifying all required payment methods are available for the locale.
See the following topics for more information:
From the Review page, review the order details and confirm the previously submitted data is present and accurate, including:
The required legal text and disclosures (Terms of Sale, privacy policy, and so on) appear as expected, and links to the accompanying legal pages are functioning.
The products (including pricing, discounts, and quantities)
The payment method (for example, the payment method type and the last four digits of the card number)
The billing and shipping addresses
The selected shipping method
Verify the content in the Order Summary accurately reflects the shopper's order and that the order number appears (if required).
When using a test credit card for a live order and the Test Order flag (testOrder
) is set to false
, confirm that you received an "Auth Failed" error message.
When using a valid credit card for a live order and the Test Order flag (testOrder
) is set to false
, confirm you received a successful payment authorization and order submission.
Note: Check the submitted order to ensure the Test Order flag (testOrder
) is not present in a live order. Essentially, you need to confirm that the Test Order flag (testOrder
) is not set to true
when you go live.
Verify that you received an order confirmation email.
The Test Order flag (testOrder
) is set to false
.
The submitted data is present in the order and accurate, including:
The products (including pricing, discounts, and quantities)
The payment method (for example, the payment method type and the last four digits of the card number)
The billing and shipping addresses
The selected shipping method
Confirm an or was generated and that the Checkout pages and API requests use HTTPS.
Confirm the .
See for more information.
Verify that the expected products, currency, pricing, and discounts . For more information, see .
Confirm the worked as expected.
Confirm the worked as expected.
[Required if you are using coupons.] Submit a promo code (promoCode
) that is either valid or invalid) and confirm the worked as expected. If the store supports promo codes that trigger orders, line items, and shipping discounts, we recommend testing all promo code types from checkout to order completion. See for more information.
Confirm the as expected.
Confirm the was generated as expected.
[Required for physical products.] Submit a shipping address from the Shipping Address page and confirm the works as expected. We recommend that you manually enter the address without using the Form Filler. For more information, see .
[Required for physical products.] Confirm the available as expected and on the Shipping Method page.
Confirm as expected, and a .
Confirm the as expected.
Submit the order and confirm the by sending a test payment.
When submitting a live order for production validation, verify the following information in the Submit Cart response or the platform to look up order information (for example, ).
You captured the .
Confirm the (termsOfSalesAcceptance
) works as expected. See the for more information on Terms of Sale Acceptance.