Prod Sanity Checks

Verify the items below every time there is a launch in the Prod environment.

Before verifying, ensure the following has been done first:

  • Clear cache across all languages (always required, especially when there are header and/or footer changes; when content is moved from Stage to Prod)
    • Dispatcher
    • CDN
  • Reindex Coveo for all languages

Item

Test Criteria

Governance

Notes

Item

Internal Search

Test Criteria

See Testing Coveo section

Notes

Coveo Search

Item

Page Features
(External Dependencies)

Test Criteria

  • Video Play in page component (Wistia, MediaValet)
  • PDF Download (AEM Assets, Marketo)
  • Social Share (AddThis)
  • Chatbot Configuration (Drift Live Chat)
  • Cookie Banner (TrustArc)

Governance

Notes

If content was copied from Stage to Prod during Prod launch, then re-do the following, if applicable:

  • Re-author these Coveo fields: ???

Item

Page Features
(Links)

Test Criteria

  • Global Navigation
    • Language Selector
  • Secondary Navigation
  • Smart Button
    • Primary Button
    • Secondary Button
    • Link Style as Text
    • Link Style as Pop-Up Video
  • Tabs
  • Text
    • In-page links

Governance

Notes

Item

Page Features
(Dynamic Content)

Test Criteria

Notes

Item

Publishing

Test Criteria

  • Publish new page
  • Edit existing page image and text
  • Delete page
  • Edit page with dynamic Card Properties

Notes

  • Do testing in AVEVA Sandbox
  • Make sure test pages are tagged for "No Index" and "Hide from Coveo" so they do not accidentally show up in external or internal search

Item

Third-Party Integrations

Test Criteria

  • How is Smartling integration tested?
  • How is Adobe Target integration tested?
  • How is Adobe Analytics integration tested?
  • How is Trust Arc integration tested?
  • Coveo (Internal Search)
  • Marketo
  • MediaValet

Governance

  • Smartling (Translation)
  • Adobe Target (A/B Testing)
  • Adobe Analytics
  • TrustArc (Cookies)
  • Coveo
  • Marketo
  • MediaValet

Notes

Item

Content Security Policy (CSP)

Test Criteria

On a live AEM web page, do Inspect > Console to confirm if violations have been fixed or to assess if new violations have occurred

Governance

Notes

Item

Sitemap.xml

Test Criteria

Governance

  • Page Properties
    • Refer to "Site Configurations" section for xml link inventory
    • Refer to "Site Configuration" section for No Index inventory

Notes

Key terms to look for to identify issues in sitemap.xml:

  • campaigns
  • events (only main page may be indexed)
  • global-alliances (only partner subpages can show, but not next level down)
  • governance
  • representative (only as it applies to the representative test pages)
  • sandbox
  • test
  • webinars
  • white-papers

Item

Sitemap Web Page

Test Criteria

  • Check each language site for any broken links or odd behavior

Notes

Item

External Report Crawl
(ad hoc; weekly report runs on Mondays)

Test Criteria

  • Fix any errors (301, 404, 500)
  • Audit for /language-masters/ URLs on live site
  • Audit for href hierarchy issues
  • Verify any launch-specific checks

Governance

Notes

Item

Browser Testing

Notes

  • Browser testing is supposed to be done by vendor before launch