You have created your variations in our graphical editor and are ready to launch your test.
Before you do, you need to test or QA your test.
To test your test, you have 2 test modes:
IP inclusion targeting
This method allows you to limit your test’s visibility to users who share a specific IP address, typically that of your organisation or company. This is very practical if you want to receive a test in real condition but you want it to be only visible to other collaborators who need to validate the recipe before final upload.
This test method is useful if you want to test more complex test scenarios, such as multi-page tests that require navigating through several pages, or on different devices (PC, mobile, tablet).
You can find IP targeting in "Add Targeting" in the Visitors section. You can specify your IP address (which appears under the targeting name) or your range of IP addresses in the test targeting options. You can specify multiple IP addresses if necessary (e.g. your organisation, your branch or another technical service provider). You can combine this targeting criterion with others.
In Traffic Modulation, assign 100% of the traffic to the variation you want to test, so you can be sure of accessing to the desired page directly.
You start the test in production (it will only be visible on your IP) and open a browser window with the targeted URL. Indeed, to test by IP, you must empty these caches or test in private browsing to ensure you reach the desired variation.
Once the test is complete and the GO for deployment is given, be sure to remove IP targeting and save; also, be sure you change the modulation and publish it so that your script is updated.
This last method lets you test in real conditions and only on the browser to which you add the cookie. This is useful if you want to test more complex test cases, such as multi-page tests, and do not want to open the test to all your employees sharing the same IP from the start.
In this case, the test is activated but only displayed for users with a specific cookie on their browser. You define the name and value of this cookie yourself in the targeting interface and then create this cookie on your browser to be assigned to the test. The procedure to follow is detailed below.
- Add a cookie targeting in your test settings.
Enter a cookie name and value as shown below. Make sure you give your cookie a neutral name like "cookie_test", "beta_test" or "test_ab". If you add a cookie name that is already on your site, the user will be tested. Do not forget to save your changes and publish your test in production.
- Be sure you are assigned to the variation
Assign 100% of the traffic to the variation you want to test so you are sure to see it. Publish your test and wait 2 minutes for your script to update.
- Now you need to add the cookie to your browser
You can do this manually or by using the Edit this Cookie plugin.
- To add the cookie manually in your browser
To add the cookie manually, load the page targeted by your test in your browser, open your console (F12) and add the following line: document.cookie="cookiename=cookievalue". Press "Enter" then refresh your page, you will be assigned to the test and the variation. You can then check that everything is correct.
- To add the cookie with the "Editthiscookie” plugin
You can also add this cookie by using a plugin (ex: Editthiscookie for Chrome). Once the plugin is installed, go to the page to be tested, click on the cookie to the right of your address bar and then on the "+". Add the cookie’s name and value. Confirm and refresh the page to be assigned to the test.