Agentic AI Atlasby a5c.ai
OverviewWikiGraphFor AgentsEdgesSearchWorkspace
/
GitHubDocsDiscord
iiRecord
Agentic AI Atlas · post-deploy-visual-check
lib-process:devops-sre-platform--post-deploy-visual-checka5c.ai
Search record views/
Record · tabs

Available views

II.Record viewspp. 1 - 1
overviewjsongraph
II.
LibraryProcess overview

lib-process:devops-sre-platform--post-deploy-visual-check

Reference · live

post-deploy-visual-check overview

Post-deploy visual check — after a production deploy, spin up Playwright against the live URL, walk a configurable set of critical flows, capture full-page screenshots, and emit a self-contained HTML report so a human reviewer can verify the deploy looks right before handing off. Motivation: traditional smoke tests (HTTP 200, login form renders) often pass while a production-only UX regression slips through. The canonical example: a banner that renders conditionally on a flag set by the server for new fallback-draft records; the banner CSS ships fine, the server flag ships fine, but the pair isn't exercised because the e2e suite uses seeded fixtures that never hit the fallback path. A quick visual walk of 4–6 critical flows catches this.

LibraryProcessOutgoing · 7Incoming · 0

Attributes

displayName
post-deploy-visual-check
description
Post-deploy visual check — after a production deploy, spin up Playwright against the live URL, walk a configurable set of critical flows, capture full-page screenshots, and emit a self-contained HTML report so a human reviewer can verify the deploy looks right before handing off. Motivation: traditional smoke tests (HTTP 200, login form renders) often pass while a production-only UX regression slips through. The canonical example: a banner that renders conditionally on a flag set by the server for new fallback-draft records; the banner CSS ships fine, the server flag ships fine, but the pair isn't exercised because the e2e suite uses seeded fixtures that never hit the fallback path. A quick visual walk of 4–6 critical flows catches this.
libraryPath
library/specializations/devops-sre-platform/post-deploy-visual-check.js
specialization
devops-sre-platform
references
  • - Playwright: https://playwright.dev/ - The "tests pass, users notice the bug" problem — see cookbook-retrospect.md in library/reference for the motivating incident report.
example
const result = await orchestrate('specializations/devops-sre-platform/post-deploy-visual-check', { productionUrl: 'https://myapp.example.com', flows: [ { name: 'Home', slug: 'home', path: '/' }, { name: 'Login', slug: 'login', path: '/login', assertions: ['magic link'] }, { name: 'Settings', slug: 'settings', path: '/settings' }, ], reportDir: '.a5c/reports', projectDir: process.cwd(), });
usesAgents
  • general-purpose

Outgoing edges

lib_applies_to_domain1
  • domain:devops·DomainDevOps
lib_belongs_to_specialization1
  • specialization:devops-sre-platform·Specialization
lib_covers_topic1
  • topic:continuous-deployment·TopicContinuous Deployment
lib_implements_workflow1
  • workflow:release-management·Workflow
lib_involves_role2
  • role:devops-engineer·Role
  • role:qa-engineer·RoleQA Engineer
lib_requires_skill_area1
  • skill-area:deployment-infrastructure-management·SkillAreaDeployment and Infrastructure Management

Incoming edges

None.

Related pages

No related wiki pages for this record.

Shortcuts

Open in graph
Browse node kind