Regression morning after. When you discover an

Regression Testing – Regression testing is the act of testing previously developed software to ensure that a new release does not inadvertently break it. Because this means testing the same thing again and again, automated testing is will become your best friend. Enter ObservePoint. If you work in an organization in which you always find out about a release after it breaks the analytics tagging, then do these two things: schedule a weekly audit and setup web journeys to run weekly. You can set these up to email you the results. If your releases are typically on the same day of the week, then schedule these to run the morning after. When you discover an issue, fix it if you can (in your tag manager most likely) or involve the appropriate resources to fix it. You may need to escalate bigger issues to the development lead. If it is going to take more than twenty-four hours to fix:Send a brief note to your analysts of the data will be missing and when you expect it to be available again.Work on the fix, bringing in development resources if necessary.Don’t forget to follow-up with the analysts when the data is available again.If you can fix it the same day:Fix it!Notify the development team of what caused the issue and that it is fixed.Send a brief note to the analysts of the data that was missing and for how long and that the issue is fixed.At the end of the day, your proactiveness will bring visibility to analytics and show the organization that you care and that you take responsibility. After doing this a few times, don’t be surprised if your development dead starts including you in the release cycle. Pre-Release Testing – If you can access your staging environment publically with or without a login, you can setup web journeys with ObservePoint. Audits – An audit will crawl your site and look for all sorts of predefined tags. If at least one tag for a vendor exists, it will tell you if any pages are missing that tag. Web Journeys – A journey allows you to track interactions with a process and check various tag elements at any step of the flow. Using CSS Element IDs Only? – ObservePoint’s interface only makes it easy to execute button clicks or populate fields using the element ID. In my experience, ID’s are not added very often to elements. While it is recommended that ID’s be unique, it is not enforced by browsers. You will have to know how to execute clicks or fill in fields using Javascript based on other CSS element attributes, e.g. class, and I will show you how.