Summary / TL:DR: This article will introduce the best practices when placing test orders from order forms in WMC.

11 min read

1 Recommendations
2 Adding Clear Cache Extensions for Chrome or Firefox
3 Using an Incognito Window When Testing
4 Testing in Different Browsers
5 Disable Caching Using Chrome Developer Tools (Advanced)
6 Test Credit Card Numbers
7 Test SEPA Accounts
8 Test Direct Debit Accounts
9 Understanding Browser Sessions in Funnelcake
10 Preview, Line Preview, and Funnel Preview Differences
11 Testing on Internal and External Networks
12 Testing Pre-Auth in Staging
13 Testing Pre-Auth in Production
14 Wrap up

Recommendations

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 application.

Browser Caching can be defined as:
A temporary storage area in memory or on disk that holds the most recently downloaded Web pages. As you jump from Web page to Web page, caching those pages in memory lets you quickly go back to a page without having to download it from the Web again. In order to ensure that the latest page is displayed, the browser compares the dates of the cached page with the current Web page. If the Web page has not changed, the cached page is displayed immediately. If the Web page has changed, it is downloaded, displayed and cached.

Adding Clear Cache Extensions for Chrome or Firefox

Adding Click & Clean for Chrome

From a Chrome browser, open the following link in a new window: Clear Cache for Chrome.
Click
Select
In the new browser tab, select
Close the browser tab to save your settings.

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

Adding Click & Clean for Firefox

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

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

Using an Incognito Window When Testing

For Chrome

Right-click on Chrome in the task bar
Select New incognito window
Paste the order link in the address bar of the incognito window

Note:
Steps one and two can be accomplished in Chrome by using the shortcut ctrl+shift+n

For Firefox

Right-click on Firefox in the task bar
Select New private window
Paste the order link in the address bar of the incognito (private) window

Testing 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.

Disable Caching Using Chrome Developer Tools (Advanced)

Open Chrome and hit F12 on your keyboard. This will open Chrome DevTools.
Click the ellipse at the top-right corner of the DevTools screen.
Select
Under the Preferences tab, within the Network section, make sure Disable cache is enabled.

Test Credit Card Numbers

This is because we integrate with a Spreedly iFrame to host the CC number. Since this field is an iFrame, we cannot know what the number is and therefore had to divert this functionality into another field (which we chose the Cardholder Name). The following information can be used on the Order Page to submit an order without running Pre-Authorization. This will assist in the testing the Journey works as expected based on the different interactions and validating that an order can be sent to BOSS/OSM/Advantage. This can be used in Production and UAT.

If you need to test Pre-Authorization, see the data further below in this document.

Cardholder Name

Notes

Test without Boss

Will skip pre-auth, Kount, and BOSS. Allows user to navigate Journey without integration dependencies.

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

Test Boss

Will skip Pre-Auth and Kount, but send the order to BOSS.

This is Equivalent to the 4242 4242 4242 4242 and 4444 3333 2222 1111 CC's in OPIUM.

Test SEPA Accounts

Test Direct Debit Accounts

Understanding Browser Sessions in Funnelcake

When a user loads a Funnelcake order page in a web browser, a Funnelcake session is created between the browser and the application. If a new Funnelcake session is needed, for testing purposes for example, it is important to close the previous browser used for a Funnelcake session and open a new browser (preferably in an incognito window) to execute another test.

Preview, Line Preview, and Funnel Preview Differences

Testing on Internal and External Networks

Testing Pre-Auth in Staging

Testing Pre-Auth in Production

WMC Support

eComm Testing Best Practices

Table of contents