Adobe Experience Manager Sites & More

Prithwiraj_Deb · 9/25/24

I was working with Chrome Dev Tool- Console tab to do some data layer testing. When Console throwed an error where an image thumbnail of an embedded product video is showing an error.

I went to the product page in the site and show the video does not have a thumbnail - obviously because referred thumbnail in AEM DAM is not found and server is throwing a 404 error.

My question is having a automated testing tool which can crawl through the entire site and list all such broken internal DAM or CloudFront links. I am not a QA person and my team is extremely lean without dedicated QA resource. Any help would be appreciated.

The video without Thumbnail

daniel-strmecki · 9/25/24

Hi @Prithwiraj_Deb,

I would actually recommend you a combination of two tools:

Sentry for monitoring your frontend, it can report JS console errors and other issues your real end users experience, see https://sentry.io/
Cypress or Playwright for UI automation testing, see https://www.cypress.io/ and https://playwright.dev/

Sentry might be a quick win for you, it doesnt cost much and is easy to set up. However, I highly recomend also automating UI tests, but this is significatly more effort as you actually need to write the tests. Since you dont have a dedicated QA, potential setup is to have the FE devs develop UI tests.

Hope it helps,

Daniel

Prithwiraj_Deb · 9/25/24

Thank you !! I have started to explore Sentry as a tool.

sarav_prakash · 9/26/24

Most of spider crawler tools are paid. Screamingfrog is very good crawler. I have used Xenus sleuth a freeware that crawls upto 500 links for free and then asks to pay.

Google webmasters also provide a crawl error tool.

But be ready to pay for all these crawler solution.

Now I implemented a reverse solution for my site. Weekly every sat night, have a Jenkins job that runs xpath query at publisher for image component with non-empty filePath property. Then collect all the filePaths; transform to publish link and place a HEAD request looking for non-200s. Finally reports which page and filepath is broken. All this runs outside AEM on the Jenkins server as python script. Possible to run entirely inside publisher also.

Other ways might be analytics, dynatrace/newrelic reports as well. Better to first check if your organization seo/analytics/devops any team are already generating such failure reports. Usually this is common requirement to report 404s.