<< Back to Summary

Standard TiQ Setup, 'utag loader' Template Edit Missing, User Opts Out

noview_no-utag-edit_opt-out.js

A Tealium iQ setup with the noview setting active, where the TiQ operator has failed to edit utag.loader template (misconfiguration case).

No tags should fire regardless of user choice, this test confirms the opt-out case.

Browser Chrome 86.0.4240.75 (Mac OS X)
Start Wed Nov 04 2020 14:31:44 GMT+0100 (Central European Standard Time)
End Wed Nov 04 2020 14:32:40 GMT+0100 (Central European Standard Time)
Duration 00:00:55
LiveConnect Recording https://app.observepoint.com/manual-journey/3962/23345
Sauce Labs Recording https://app.eu-central-1.saucelabs.com/tests/6f931aafb87b4ec396b799bf59adcd65
Results Summary
Passed Skipped Failures
21 0 0

 STEP 1 - initial visit to test page00:00:12

5 Test(s):
should navigate to the page00:00:11 
Navigated to https://solutions.tealium.net/hosted/usercentrics/test-page-noview-no-utag-edit.html
 
On landing
 
(Click screenshot to expand)
should have the correct title00:00:00
should have a utag_main cookie00:00:00 
TiQ will run because we can't detect the edit before load, but no tags should be fired.
should have a visible Usercentrics banner00:00:00
should have the current version of the Usercentrics integration running00:00:00

 STEP 2 - fire virtual page view by clicking button00:00:05

1 Test(s):
should click the button to fire tracking00:00:05

 STEP 3 - fire virtual page view to tag 10 only by clicking button00:00:05

1 Test(s):
should click the button to fire tracking00:00:05

 STEP 4 - deny tracking00:00:05

2 Test(s):
should deny tracking00:00:05
should NOT have a visible Usercentrics banner anymore00:00:01 
After decision.
 
(Click screenshot to expand)

 STEP 5 - fire virtual page view to tag 11 only00:00:05

1 Test(s):
should fire the virtual view to tag 1100:00:05

 STEP 6 - fire virtual page view to tags 7 and 11 only00:00:05

1 Test(s):
should fire the virtual view to tags 7 and 11 only00:00:05

 FINALIZE - get Proxy logs to confirm tag firings00:00:18

2 Test(s):
finish the run and get the logs00:00:18
should generate the filtered logs00:00:00 
{
  "allSteps": [],
  "step1": [],
  "step2": [],
  "step3": [],
  "step4": [],
  "step5": [],
  "step6": []
}

 VERIFY - check the network logs to make sure no tags fired at any point in this test.00:00:00

8 Test(s):
basic log validation00:00:00
Tag 6 should NOT have fired at any point in this test00:00:00 
Missing map should mean that no tags fire, no matter what.
Tag 7 should NOT have fired at any point in this test00:00:00 
Missing map should mean that no tags fire, no matter what.
Tag 8 should NOT have fired at any point in this test00:00:00 
Missing map should mean that no tags fire, no matter what.
Tag 9 should NOT have fired at any point in this test00:00:00 
Missing map should mean that no tags fire, no matter what.
Tag 10 should NOT have fired at any point in this test00:00:00 
Missing map should mean that no tags fire, no matter what.
Tag 11 should NOT have fired at any point in this test00:00:00 
Missing map should mean that no tags fire, no matter what.
Tag 15 should NOT have fired at any point in this test00:00:00 
Tag 15 is not configured in the mapping, so it should never fire

This report has been generated by Tealium's automated testing platform.

These tests will have been created specifically for your project by a Tealium Implementation Engineer to verify a configuration or use case.

The intent is to document the tests run on the completed configuration (acceptance tests). It can also serve as a limited regression test as work continues, to ensure that future projects don't break previous ones. For more information, see the developer documentation.