/
WMC eComm Testing Best Practices

WMC eComm Testing Best Practices

This article covers best practices when placing test orders in WMC.


Table of contents


Things to Remember

Production Organizations vs UAT Organizations

It’s important to know if you’re working and testing in a production environment vs a UAT environment. This will determine how your tests are processed and where they will end up.

Until it’s your organization's turn to onboard, you will only have access to your UAT organization.

Production Environments

WMC Production environments are connected to the production environments of all other applications needed for an order to successfully process. When checking to confirm a test order has processed successfully, you will want to check the Advantage Production area.

UAT Environments

WMC UAT environments are connected to the UAT environments of all other applications needed for an order to successfully process. Some things to keep in mind are these environments might not be as up-to-date as production environments. For example, Advantage Train is not refreshed as often as production, so choices (among other things) might not be available. When checking to confirm a test order has processed successfully, you will want to check the Advantage Train area. Please note only orders placed using the Vantiv test credit card numbers will be processed and visible in Advantage Train.


Browser Caching

Why?

A common issue that many WMC users experience during order form testing is browser caching, causing inconsistent or inaccurate results. For example, a user may load an order form and discover there is a typo in the copy. They will close the browser tab where the order form was loaded, fix the typo, re-publish the creative, and then load the order form again. At this point, they may see that the typo is still visible on the page. This is a result of the browser caching the previous version of that order form - it is not an issue with the WMC application.


To avoid any issues related to browser caching, here are some suggestions:

  • Use an Incognito Window When Testing

Opening an incognito window will allow you to test without the browser saving your site visit information.

  1. Right-click on 

     in the task bar.

  2. Select 

  3. Paste the order link in the address bar of the incognito window.

  1. Right-click on 

     in the task bar.

  2. Select 

  3. Paste the order link in the address bar of the incognito (private) window.

Clear Cache is an app that allows you to clear your browser cache easily with one click.

  1. From a Chrome browser, open the following link in a new window: Clear Cache for Chrome.

  2. Click

  3. Select

  4. In the new browser tab, select

  5. Close the browser tab to save your settings.

The extension will appear to the right of the address bar.

  1. From a Firefox browser, open the following link in a new window: Clear Cache for Firefox

  2. Click

  3. Click

Once the browser has reopened, the extension will appear to the right of the address bar.

  • Disable Caching Using Chrome Developer Tools (Advanced)

Chrome Developer Tools include an option to disable caching for the active browser as long as the Developer Tools window is open simultaneously.

This works in Chrome only.

1. Open Chrome and hit F12 on your keyboard.  This will open Chrome DevTools.

2. Click the ellipse at the top-right corner of the DevTools screen.

3. Select Settings

4. Under the Preferences tab, within the Network section, make sure Disable cache (while DevTools is open) is enabled.

  • Test in Different Browsers

Since sessions across browsers are completely separate, using multiple browsers will reduce the amount of cache clearing you'll have to do.  You may have to clear each browser's cache if your tests require you to open the same link multiple times in each browser.


Testing on Internal and External Networks

Why?

When creating a new domain, campaign, or any other type of content, it is important to run multiple tests from multiple networks and devices to ensure all parties are able to see it as expected. It is possible that certain networks, such as Agora vs non-Agora, will behave differently. 

  1. Test on a desktop on the internal network

  2. Test on a desktop on an external network

  3. Test on a mobile device on the internal network

  4. Test on a mobile device on an external network

  5. Test the entire process, from IRIS to WMC

  6. Test that the URL is redirected from a non-secure to a secure


Previewing Work

Why?

There are several preview options available in WMC and each behaves differently. It’s important to keep this in mind and chose the option that aligns best with what you’re trying to see.

To preview the page with all content and data elements, as a customer would experience, you will need to save the creative and go to the content section and click on the customer experience preview link. This version of the Preview is a static page and will not allow you to select hyperlinks to place an order or move onto another page via the Yes/No links. 

The 'Live Preview' option in the code editor will open a new web browser and renders the HTML-related information as you are typing; however, it will not display the conditional data, such as data placeholders.

To experience the entire Journey as a customer would, you will need to utilize the "Journey Preview" link or the effort link that exists on the Journey or Effort Page. This link will allow you to navigate through the entire Funnel, place orders, and receive confirmation emails.


Select the Testing Scenario that Best Suits Your Needs


I am just validating the flow of the funnel
(for UAT and Production Environments)

If you’re only concerned with scaling internal testing to validate the functionality/customer journey and don’t need to validate order processing, use these instructions to skip the authorization and fraud process. This can be used for both production and UAT WMC organizations.


What you will need:

  1. One of the Billing First Names listed below

To sidestep integration dependencies with order processing.

2. A valid email address

To send confirmation emails to people placing test orders. To avoid duplicate order error messages be sure the use a different email address with each test order.


While all of the other fields on the order form are required, they are not important for testing journey functionality.

1. Open the link to the effort you are testing and navigate to the order form.

2. Enter the following into the First Name field within the billing address section:

Billing First Name

Notes

SkipPreauthAndBoss
skipall

Entering either of these values into the first name field in the billing address will skip pre-auth, Kount, and BOSS. Allows user to navigate Journey without integration dependencies.  The order will not be processed or show in Advantage.


This is the Equivalent to the 4111 1111 1111 1111 CC in OPIUM. 

The functionality of both values is the same. Skipall was just created to be a shorter, simpler alternative.

Confirmation emails will trigger for these orders, so be sure to use a valid email address. 

To avoid duplicate order error messages be sure the use a different email address with each test order.

3. Next, enter a valid email address

This can be used in Production and UAT. 

What does this do?

This bypasses all integrations with PayGate and Advantage and directs customers from one page to another while still allowing for the conditional data to render as expected for customer interactions.

 


I am doing a complete test in a WMC Production Organization
(including processing the order)

We recommend testing every effort before launching. Test versions can be used for initial testing but it’s best to validate the real, live effort(s) as well.

Due to the fact that we are calling real banks to validate CC's in Production, the Vantiv test credit card data listed below cannot be used for validation. Instead, you'll need to utilize real credit cards or specific test data to bypass the fraud and authorization process. Once the test order is placed and processed, it will appear in Advantage Production.

Before you being placing your test order, verify/be mindful of a couple of things:

One common occurrence we have run into is that the Promo Code and Offer Code are not aligned when activating orders in OSM. This happens when the user generates a Promo Code in WMC, but then subsequently changes the Offer Code or the Order Page on the effort. To minimize this risk, you should ensure the offer code is consistent after generating the Promo Code and before even considering placing a test order.

When testing in Production, you will often times hit a snag with Kount marking your persona as potentially fraudulent. To ensure you don't run into this situation, reach out to the EPP team to get your email address(es) whitelisted within Kount to ensure they are approved every time!

To successfully place a test order in a production environment:

  1. Open the link to the effort you are testing and navigate to the order form.

  2. On the order form, begin filling out the billing address section. In this section, use REAL addresses.

Advantage utilizes an address verification tool to process their orders for optimal success.

If you don't want to utilize your own address, an alternative option is to use a restaurant address. Perform a simple google search to acquire a restaurant in a random city/state. 

Random address generators are not always successful.


I am doing a complete test in WMC Production Organization (including processing the order) AND I want to simulate a new customer experience

In addition to everything covered in the section above (I am doing a complete test in a WMC Production Organization (including processing the order)), you'll need to use a new, unique email address to ensure the order isn't (immediately) consolidated with an existing account so you can test the new customer journey/experience. A good example of a use case for this is when you are using a magic link to have a customer set up their new username and password (versus requesting it on the order form) and want to test it.

You can continuously create new email accounts OR, an easier more efficient way is to use a Gmail hack (steps found below). This will 'trick' the middleware capsule system for the initial order, simulating a new customer so that you can test that use cases are working as intended. Eventually, once the order is processed in Advantage, the Gmail hack email/account will (likely) be consolidated to the existing, real account*, so you won’t have a lot of unlinked accounts. 

*Exception: if a different name or address is used on the order form then the new account may not be consolidated with the existing one 

Gmail hack

  • Add “+1” (or any numbers/letters) to the end of the Gmail handle.

Example:

Real Gmail handle: Johnsmith@gmail.com 

Gmail hack: Johnsmith+11321@gmail.com 

  • The site will create new/unique customer 

  • An email goes to the original Gmail inbox

You do not need to whitelist the Gmail hack email addresses, just the real email address.


I am doing a complete test in a WMC UAT Organization
(including processing the order)

You can do a complete end-to-end test using your affiliate’s UAT environment. Once you have set up a journey in the UAT environment, a test order can be placed. Once the test order is placed, it will appear in Advantage Train.

To successfully place a test order in a UAT environment:

1. Open the link to the effort you are testing and navigate to the order form.

2. On the order form, begin filling out the billing address section. In this section, use REAL addresses.

If you don't want to utilize your own address, an alternative option is to use a restaurant address. Perform a simple google search to acquire a restaurant in a random city/state. 

Why?

Advantage utilizes an address verification tool to process their orders for optimal success.

3. For testing purposes, UAT is set up to trigger the different Kount statuses using specific rules. If there is a specific Kount status you wish to trigger enter the appropriate information from the “Rule” column into the specified field on the order form.

Kount Status

Rule

Process Order?

Error Message to Customer

Approved

Just don't use the below values

Yes

N/A

Review

Billing and Shipping Postal Code equals 22222

Yes

N/A

Escalate

First and /or Last Name of the customer contains 'Test'

Yes

N/A

Decline

Billing Postal Code starts with 11111

No

This order cannot be processed. Please contact your bank for further assistance.

 

4. Once you reach the payment section, you might want to attempt processing an order to trigger a specific response code. Use the test information for the payment type you’d like to test below. 

You should not use real credit cards because the UAT environments will not recognize them which will prevent you from being able to place a test order and validate it in Advantage.

Testing Data for Vantiv Processor:

Response Code

Credit Card Type

Credit Card Number

Response Message

Order Page Error Message

Pre-Auth Status

000

VI

4457000800000002

Approved

N/A

APPROVED

000

VI

4457000900000001

Approved

N/A

APPROVED

000

VI

4457001000000008

Approved

N/A

APPROVED

000

MC

5112000900000005

Approved

N/A

APPROVED

101

MC

5112001000000002

Issuer Unavailable

N/A

APPROVED

101

VI

4457002700000009

Issuer Unavailable

N/A

APPROVED

101

VI

4457003000000004

Issuer Unavailable

N/A

APPROVED

101

MC

5112002000000000

Issuer Unavailable

N/A

APPROVED

Response Code

Credit Card Type

Credit Card Number

Response Message

Order Page Error Message

Pre-Auth Status

110

VI

4457002100000005

Insufficient Funds

We were unable to successfully charge your credit card. Please contact issuing bank for assistance.

NOT_APPROVED

120

AX

375000030000001

Call Issuer

We were unable to successfully charge your credit card. Please contact issuing bank for assistance. 

NOT_APPROVED

120

VI

4457001200000006

Call Issuer

We were unable to successfully charge your credit card. Please contact issuing bank for assistance. 

NOT_APPROVED

120

VI

4457001300000005

Call Issuer

We were unable to successfully charge your credit card. Please contact issuing bank for assistance. 

NOT_APPROVED

120

VI

4457001400000004

Call Issuer

We were unable to successfully charge your credit card. Please contact issuing bank for assistance. 

NOT_APPROVED

120

VI

4457002200000004

Call Issuer

We were unable to successfully charge your credit card. Please contact issuing bank for assistance. 

NOT_APPROVED

123

DI

6011000400000000

Call Discover

We were unable to successfully charge your credit card. Please contact issuing bank for assistance.

NOT_APPROVED

301

MC

5112001600000006

Invalid Account Number

This appears to be an invalid credit card number. Please check your card number and try again.

NOT_APPROVED

301

MC

5112001700000005

Invalid Account Number

This appears to be an invalid credit card number. Please check your card number and try again.

NOT_APPROVED

301

VI

4457000100000000

Invalid Account Number

This appears to be an invalid credit card number. Please check your card number and try again.

NOT_APPROVED

303

VI

4457002000000006

Pick Up Card

We were unable to successfully charge your credit card. Please contact issuing bank for assistance.

NOT_APPROVED

305

MC

5112001900000003

Expired Card

This appears to be an expired credit card.  Please try a different credit card.

NOT_APPROVED

321

VI

4457001900000009

Invalid Merchant

We were unable to successfully charge your credit card. Please contact issuing bank for assistance.

NOT_APPROVED

321

MC

5112001800000004

Invalid Merchant

We were unable to successfully charge your credit card. Please contact issuing bank for assistance.

NOT_APPROVED

322

VI

4457002800000008

Invalid Transaction

We were unable to successfully charge your credit card. Please contact issuing bank for assistance.

NOT_APPROVED

340

VI

4457002500000001

Invalid Amount

We were unable to successfully charge your credit card. Please contact issuing bank for assistance.

NOT_APPROVED

349

VI

4457002300000003

Do Not Honor

We were unable to successfully charge your credit card. Please contact issuing bank for assistance.

NOT_APPROVED

350

AX

375000050000006

Generic Decline

We were unable to successfully charge your credit card. Please contact issuing bank for assistance.

NOT_APPROVED

350

VI

4457002900000007

Generic Decline

We were unable to successfully charge your credit card. Please contact issuing bank for assistance.

NOT_APPROVED

 


Still need help?

We know this can be frustrating. To get further help please open a Support ticket.

Click here to open a ticket


Related Content


Cannot find the article you’re looking for?

Suggest a new article here!

 

Related content

com.atlassian.confluence.content.render.xhtml.migration.exceptions.UnknownMacroMigrationException: The macro 'html-macro' is unknown.