WMC eComm Testing Best Practices
This article covers best practices when placing test orders in WMC.
Table of contents
- 1 Things to Remember
- 2 Select the Testing Scenario that Best Suits Your Needs
- 2.1 I am just validating the flow of the funnel (for UAT and Production Environments)
- 2.2 I am doing a complete test in a WMC Production Organization(including processing the order)
- 2.3 I am doing a complete test in WMC Production Organization (including processing the order) AND I want to simulate a new customer experience
- 2.4 I am doing a complete test in a WMC UAT Organization(including processing the order)
- 2.5 Related Content
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.
Clear Cache is an app that allows you to clear your browser cache easily with one click.
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.
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.
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.
Select the Testing Scenario that Best Suits Your Needs
I am doing a complete test in a UAT environment (including processing the order)
I am doing a complete test in a Production environment (including processing the order)
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:
One of the Billing First Names listed below
2. A valid email address
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.
|
3. Next, enter a valid email address
I am doing a complete test in a WMC Production Organization
(including processing the order)
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:
To successfully place a test order in a production environment:
Open the link to the effort you are testing and navigate to the order form.
On the order form, begin filling out the billing address section. In this section, use REAL addresses.
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.
The site will create new/unique customer
An email goes to the original Gmail inbox
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.
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.
Related Content