Automating Adobe Analytics QA Part 1: The Simplest Solution | Cameron Tarle

Introduction:

You work in Adobe Launch implementation, and you’re sick of seemingly redundant QA. I understand, it is exhausting sometimes when you need to repeat tasks. Worse yet, because this work is unengaging your margin of error increases. In this three part series I want to assist you in finding an automation solution that works for your client, and product maturity, without resorting to expensive audit tools.

First, we will be covering just making a simple test on selenium IDE, a chrome extension your developer QA colleagues should be familiar with, to check if rules are firing. This may be all you need to get by, but there’s more that can be automated: In the second part we will make a python script that crawls pages on the site to not only check what rules are firing, but also if data elements are populating. Then, in the final part we will be combining our knowledge to make a test that checks data elements, variables, rules, and pages to create test results that we can compare with previous builds.

This is a tall order, but actually for this first part of our series you do not need to know much code. Instead, today we need a basic understanding about how Adobe Launch works, how your site works, and familiarity with a few chrome extensions.