#Site Infrastructure Tests
This project contains code that you can use to build your own test suite.
The suite can be used to test parts of the site infrastructure that are important for whatever your Analytics/Marketing team ads on top of it using the tag management system.
Running this suite as a regression tests effectively prevents dev from pulling the gound from under analytics feet.
A JSON file (testdescription.json) contains all pages to be tested along with their tests. If you run the test, the AllTests test suite reads that file, then generates a dynamic test suite for each page. All of those will then run.
You can specify which test description the test suite will read by specifying the test.description.file property when you run the test.
The testdescription.json file has two top level elements:
- name
- pagesToTest
The name element is used to give the test suite a name.
Example: "name": "my-test-site.com"
The pagesToTest element contains a list of pages and the corresponding tests that should be run on them.
Each sub-element of pagesToTest must contain a pageURL element. It can further contain elements that specify which tests should be run.
Those elements have two parts: the name of the test class, plus parameters that the test class can interpret. Section 2.2 and below show the test class names and parameters as currently implemented.
The pageURL element specifies which page the test should load before it executes the tests specified for the page.
Example: "pageURL": "http://test.com/"
Note: this element is mandatory
The following elements can be used to test the page itself.
Specify this element if you want to test whether the page loads jQuery.
Example: "jQueryLoaded": true
You can test the minimum version that you need on the page using this element.
Example: "jQueryMinVersion": "2.0"
You can test that the version is below a specific version.
Example: "jQueryVersionBelow": "3"
A test that allows you to test for the existence of DOM elements in the page.
Note: the parameters can be one single parameter, or a list of parameters.
Example: "elementSelectedByCSSSelectorExists": "h1"
Example: "elementSelectedByCSSSelectorExists": [ "h1", "div#author" ]
A test that allows you to test a DOM element exists exactly n times in the page.
Note: single CSS selector, only.
Example: "elementSelectedByCSSSelectorExistsNTimes": { "selector": "h1", "n": 1 }
This test allows you to test for a Javascript data layer element in the page.
Note: the parameters can be one single parameter, or a list of parameters.
Example: "dataLayerElementExists": "digitalData.page.pageInfo.pageName"
Example: "dataLayerElementExists": [ "digitalData.page.pageInfo.pageName", "digitalData.page.pageInfo.language" ]
Similar to the one above, but this one checks whether the data layer element has the right value.
Note: the parameters can be one single parameter, or a list of parameters.
Example: "dataLayerElementValue": { "name":"digitalData.page.pageInfo.pageName", "value": "Home" }
Example: "dataLayerNumericElementValue": { "name":"digitalData.page.pageInfo.pageID", "value": 896 }
Example: "dataLayerElementValue": [ { "name":"digitalData.page.pageInfo.pageName", "value": "Home" }, { "name":"digitalData.page.pageInfo.language", "value": "en" } ]
This test allows you to test for a Javascript data layer element in the page after waiting for some time. Ideal for pages that load the data layer asynchronously.
The delay is in milliseconds.
Note: the parameters can be one single parameter, or a list of parameters.
Example: "dataLayerElementDelayedExists": { "name": "digitalData.page.pageInfo.pageName", "delay": 500 }
Example: "dataLayerElementDelayedExists": [ { "name": "digitalData.page.pageInfo.pageName", "delay": 500 }, { "name": "digitalData.page.pageInfo.language", "delay": 500 } ]
Similar to the one above, but this one checks whether the data layer element has the right value. Again, this can be used on pages that load the data layer asynchronously.
The delay is in milliseconds.
Note: the parameters can be one single parameter, or a list of parameters.
Example: "dataLayerElementValue": { "name":"digitalData.page.pageInfo.pageName", "value": "Home", "delay": 500 }
Example: "dataLayerElementValue": [ { "name":"digitalData.page.pageInfo.pageName", "value": "Home", "delay": 500 }, { "name":"digitalData.page.pageInfo.language", "value": "en", "delay": 500 } ]
This test allows you to inject arbitrary Javascript code into the page and test whether it returns 'true'.
Example: "genericJavascript": "return true;"
A test that checks whether DTM has been loaded on the page
Example: "adobe.DTMLoaded": true
Testcase that checks whether DTM is in debug mode. Needed for some of the tests below, such as adobe.DTMRuleHasRun.
Example: "adobe.DTMIsInDebugMode": true
A test that checks that the site is loading the correct DTM library.
Example: "adobe.DTMLibraryName": "satelliteLib-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
This test allows you to test for a Javascript data layer element in the page.
Note: the parameters can be one single parameter, or a list of parameters.
Example: "adobe.DTMDataElementExists": "Page Name"
Example: "adobe.DTMDataElementExists": [ "Page Name", "Page Type" ]
Similar to the one above, but this one checks whether the data layer element has the right value.
Note: the parameters can be one single parameter, or a list of parameters.
Example: "adobe.DTMDataElementValue": { "name":"Page Name", "value": "Home" }
Example: "adobe.DTMDataElementValue": [ { "name":"Page Name", "value": "Home" }, { "name":"Page Language", "value": "en" } ]
This test allows you to test for a Javascript data layer element in the page after waiting for some time. Ideal for pages that load the data layer asynchronously.
The delay is in milliseconds.
Note: the parameters can be one single parameter, or a list of parameters.
Example: "adobe.DTMDataElementDelayedExists": { "name": "Page Name", "delay": 500 }
Example: "adobe.DTMDataElementDelayedExists": [ { "name": "Page Name", "delay": 500 }, { "name": "Page Language", "delay": 500 } ]
Similar to the one above, but this one checks whether the data layer element has the right value. Again, this can be used on pages that load the data layer asynchronously.
The delay is in milliseconds.
Note: the parameters can be one single parameter, or a list of parameters.
Example: "dataLayerElementValue": { "name":"Page Name", "value": "Home", "delay": 500 }
Example: "dataLayerElementValue": [ { "name":"Page Name", "value": "Home", "delay": 500 }, { "name":"Page Language", "value": "en", "delay": 500 } ]
Allows you to test whether a PLR exists in the current setup.
Note: the parameters can be one single parameter, or a list of parameters.
Example: "adobe.DTMPageLoadRuleExists": "Normal Page Load"
Example: "adobe.DTMPageLoadRuleExists": [ "Normal Page Load", "Blog Article Page Load" ]
Tests whether a DCR exists in the current setup.
See above for syntax.
A test that checks whether an EBR exists in the current setup.
See above for syntax.
Allows you to test whether a rule has actually fired.
Note: the parameters can be one single parameter, or a list of parameters.
Example: "adobe.DTMRuleHasRun": "Normal Page Load"
Example: "adobe.DTMRuleHasRun": [ "Normal Page Load", "Blog Article Page Load" ]
Allows you to test whether a rule has actually fired after a delay.
Note: the parameters can be one single parameter, or a list of parameters.
Example: "adobe.DTMRuleHasRunAfterDelay": { "name":"Normal Page Load", "delay":500 }
Example: "adobe.DTMRuleHasRunAfterDelay": [ { "name":"Normal Page Load", "delay":500 }, { "name":"Blog Article Page Load", "delay": 500 } ]
You can test whether an EBR runs as a result of triggering something in the document.
Note: current implementation only supports "click" triggers!
Note: the parameters can be one single parameter, or a list of parameters.
Example: "adobe.DTMEventBasedRuleHasRun": { "name": "Add to Cart", "triggerType": "click", "triggerElement": "button#cartAdd" }
Example: "adobe.DTMEventBasedRuleHasRun": [ { "name": "Add to Cart", "triggerType": "click", "triggerElement": "button#cartAdd" }, { "name": "Shipping Info Popup", "triggerType": "click", "triggerElement": "a#terms_conditions" } ]
A test to check whether the Marketing Cloud Visitor ID Service has loaded on the page.
Example: "adobe.VisitorIDServiceLoaded": true
Tests the version of the MCVID against a minimum version.
Example: "adobe.VisitorIDServiceMinVersion": "1.5"
You can test that the MCVID is below a certain version.
Example: "adobe.VisitorIDServiceVersionBelow": "2"
Allows you to test whether Analytics Javascript code has loaded in the page.
Example: "adobe.AnalyticsCodeLoaded": true
Tests whether the Analytics code is "AppMeasurement" or "legacy" (H.xx.y and before).
Example: "adobe.AnalyticsCodeType": "AppMeasurement"
You can test the Analytics Javascript code against a minimum version.
Example: "adobe.AnalyticsCodeMinVersion": "1.6"
Checks whether there has been a tracking request against the specified report suite.
Note: the parameters can be one single parameter, or a list of parameters.
Example: "adobe.AnalyticsTagForReportSuiteFired": "myrsid"
This works with multi-suite tagging!
Example: "adobe.AnalyticsTagForReportSuiteFired": "myrsid,myglobalrsid"
You can supply multiple rsids, which would test for multiple, independent tracking calls.
Example: "adobe.AnalyticsTagForReportSuiteFired": [ "myrsid1", "myrsid2" ]
As above, but the check happens after a delay.
Example: "adobe.AnalyticsTagForReportSuiteFiresAfterDelay": { "rsid": "myrsid", "delay": 2000 }
Supports the same features as above.
Tests whether the Target Javascript code has loaded
Example: "adobe.TargetCodeLoaded": true
Allows you to tests whether the Target global mbox with a specific name exists.
Example: "adobe.TargetGlobalMboxExists": "global-mbox"
TBD