QA & Testing tools

[cchaudet]

What tools do you use to test your tags once implemented in Tealium ? In particular, we need to test : - The variables and the tags are served in the page - The javascript is executed and send the right values to partners (ex: GA / Comscore / ESV / Zanox / ...)

[jared_hislop · Accepted solution]

Hey Camille, There are several choices here depending on what browser you are using. Let's start with tools that will show you the server calls to each vendor so you can make sure the correct data is getting passed. FireFox: - One of the best tools for FireFox is HTTP Fox. This is a free add on to Fire Fox that is pretty handy when it comes to debugging. This is specific to Fire Fox and won't work in other browsers. You can get it here: https://addons.mozilla.org/en-us/firefox/addon/httpfox/ Chrome: -I would suggest Charles. It is very similar to Http Fox but has a few extra capabilities outside of checking server calls. The downside is that it is not free. Also, you'll need to configure it to capture secure pages (https) which is an easy config. You can download it here: http://www.charlesproxy.com/download/ For both FF and Chrome, Observe Point is a pretty awesome tool that breaks out the server calls into an easy to read view. It is a free add on and you can download it here: http://www.observepoint.com/product#plugin I don't test much in IE but I believe Observe Point will work there or there is a tool called Fiddler that will work in all browser but it is only available to PC. Available here: http://fiddler2.com/get-fiddler Now for verifying the variables are served on the page correctly you also have a couple option. 1) You can use our Web Companion. Open Web Companion, Select the "Data" tab. Scroll down until you see utag_data and expand that selection. 2) I would suggest using the browser developer tools. Click on Tools in the browser and select "Developer Tools". Open up the Console and type in "utag_data" This will show you the variables that are being sent in the utag_data object on the page. Quick keys to open developer tools are : PC - hit F12 in FF or Chrome ( I wouldn't suggest IE ) Mac - hit command+option + i I hope this helps and reach out with other questions. Thanks

[dan_george]

Just to add a few more suggestions... I agree with Jared that HTTPFox is the best network logging tool for Firefox. You can filter the network log on any part of a URL whereas other tools only allow you to filter on the filename of the call. I also like to use Google Chrome's Developer Tools because of the Initiator column in the Network tab. This allows you to see which file on the page caused the selected file to run. It can help you backtrack to the root cause of an issue if, for example, your DoubleClick tag is piggybacking several tags and you need to find the script causing and issue like running a non-secure call on a secure page. Filtering for "utag" in the network logs allow you to verify utag.js is firing, as well as the specific vendor library, e.g. utag.1.js. The "1" is the tag UID and can be referenced in the UI under the Tags tab. Then you just need to filter for the call you are looking for and view the URL and/or query string parameters to verify the data being sent is correct. Both HTTPFox and Chrome Developer Tools have a simple layout for viewing query string parameters. Please know though that not all tags are alike and some require differing methods of verification.

[colin_sulin]

Chrome dev tools is by far the best for an all round debugging tool. (https://developers.google.com/chrome-developer-tools/) Firebug for firefox is pretty comprehensive(https://getfirebug.com), and Firefox also provides some dev tools but these aren't as good as Chrome (https://developer.mozilla.org/en-US/docs/Tools). You can also use JS beautifier to make the JS readable : http://jsbeautifier.org/ and JSON editor to analyze JSON data code : http://www.jsoneditoronline.org/

[iain_murphy]

Hi Camille - I don't believe there are any automatic tools per se that can do this. And you would probably want to manually check the firing of tags any how so you know what is firing (and isn't) so you can intervene accordingly.

[llgg716]

I am following up this testing question but on a different route.

Does teamlium provide APIs/endpoints that serve:

1. when I request new TraceID, then Tealium API/Endpoints responsd me a new traceID
2. when I request my event with the above new TraceID, then Tealium API/Endpoint responde me my event with JSON or other reasonable format including eVals/Props and values pairs.

I like to call these Tealium endpoints with my local test scripts, i.e javaScript, python, C# etc.