Join us for the next Community Q&A Coffee Break on Tuesday April 23, 2024 with Eric Matisoff, Principal Evangelist, Analytics & Data Science, who will join us to discuss all the big news and announcements from Summit 2024!
SOLVED
Automation of Adobe Analytics Regression testing
1 Accepted Solution
Correct answer by
There is not really an easy option here. Automation testing is not an easy thing when it comes to tagging as it would require a fair amount of set up and maintenance.
You can opt to use different automation tools out there to create automation testing like Selenium as you mentioned. I have done an example of such project using Puppeteer in the past https://github.com/alcazes/Puppeteer-with-Mocha-and-Chai . This will work best with data layer tagging implementation than DOM implementations. The reasons behind it is that DOM can change at any point and it will break your automation tests.
The best solution would be to implement a strong data layer on your platform and create a tagging that solely relies on the data layer and its events. Once it is implemented and you tested the different permutation of events and validated that rules are fired correctly then you can expect that anytime your platform developers use the same data layer event then the same rules will trigger and same data will be send. Also your platform development team deploying the data layer will write unit tests and integration tests to validate data layer is correct, by doing so they will ultimately do the automation test that you are seeking on their side.
Correct answer by
There is not really an easy option here. Automation testing is not an easy thing when it comes to tagging as it would require a fair amount of set up and maintenance.
You can opt to use different automation tools out there to create automation testing like Selenium as you mentioned. I have done an example of such project using Puppeteer in the past https://github.com/alcazes/Puppeteer-with-Mocha-and-Chai . This will work best with data layer tagging implementation than DOM implementations. The reasons behind it is that DOM can change at any point and it will break your automation tests.
The best solution would be to implement a strong data layer on your platform and create a tagging that solely relies on the data layer and its events. Once it is implemented and you tested the different permutation of events and validated that rules are fired correctly then you can expect that anytime your platform developers use the same data layer event then the same rules will trigger and same data will be send. Also your platform development team deploying the data layer will write unit tests and integration tests to validate data layer is correct, by doing so they will ultimately do the automation test that you are seeking on their side.
